Tool for Accumulating QA cases
We use Testrail as a repository of test cases to ensure that all aspects of the platform are covered. Currently, we have more than 2,800 test cases in our repository. This covers both core and non-priority modules. We regularly revise our test cases to keep them up-to-date with changes in the platform. In addition, we add new client scenarios and reproduce bugs to ensure that everything works properly.
Our QA process follows the two-week sprint cycle widely adopted in IT development. This allows us to deliver quality assurance for each user story in a timely and efficient manner. Sprint planning ensures that all stakeholders are aware of the tasks to be undertaken and the time in which they need to be completed. During the sprint, we track our progress in QA tasks and report any issues that arise. At the end, we review our results and plan for the next sprint.
This process helps us to deliver efficient quality assurance for our clients. It also allows us to effectively track our progress and identify any areas that need improvement: We are continuously working to better our process so that we can provide the best possible service to our implementation partners and B2B end-user clients.
QA Workflow on User Stories in Testrail is as follows:
1. Actualization and updating test cases for priority modules
2. Adding new coverage for low-priority modules (customer review, sitemap, etc.)
3. Adding new test cases for story or update cases for bugs (if needed)