Overview
This section serves as the single source of truth for QA-related practices and tools for EmbedIT platform projects. It offers hands-on guidelines with practical examples and templates.
What is Inside
The QA guides are built for clarity and speed, designed for everyday use by testers, developers, and everyone working in or with QA. They are structured around real-life QA deliverables, tooling setups, and team collaboration standards.
Common Use Cases
Here’s how delivery teams should use this section day-to-day:
- Follow how to log bugs that are clear, reproducible, and actionable consistently across projects.
- Establish Definition of Done (DoD) as definition of ONE QUALITY to align on what "tested" and "customer ready" actually mean.
- Learn how to set up and write mobile & web test automation re-using the existing solutions within EIT.
- Explore how to connect automated tests with development pipelines in Azure DevOps.
- Find templates for test plans, test strategies, checklists, and more for fast, effective QA.
Main Topics You'll Find Here
- Mobile Test Automation Template & Setup → A guide to get up and running with Appium and our Cucumber framework.
- Web Test Automation Template & Setup → guide to get up and running with Cucumber + Playwright setup.
- Backend Test Automation Template & Setup → guide to get up and running with our RestTest backend automation framework.
- Performance Tests Template & Setup -> guide to get up and running with performance tests and analyze results.
- QA Templates reusable templates for test plans, checklists, test case specs.
- CI/CD Integration → how to hook QA tasks and test runs into Azure Pipelines.
Conclusion
QA guides are our go-to playbook for embedding quality into project daily routine. Built from real practices used across our teams, these pages need to continuously evolve based on feedback, tool changes, and project needs. Keeping it up to date is our shared and everyone's responsibility. One for all, all for one!
Bugs & Issues
Bugs and issues in software can lead to crashes, data loss, or poor user experiences, making it essential to detect and fix them during testing. Addressing these problems early ensures a reliable, secure product, reduces costs, and protects a company’s reputation.
Rest test
Continuous API testing