Optimum-Web utilizes an Integrated Quality Assurance practice to ensure the highest quality of our deliverables. We have perfected QA strategy and methodology that blend seamlessly into the development lifecycle without crossing the important boundary between the development and software quality assurance processes.
From the beginning of the implementation process, the tasks and the features that need to be implemented are split into sprints of 2-3 weeks. At this stage, the QA person makes test scenarios for manual testing based on the specifications got, and uses them when developers finish the sprint. That ensures that we will not miss anything to test.
While programmers are writing the functionality code, the QA specialist is writing a test code for this functionality. This is our second test level.
So the QA flow we use is the following. First, we are running automated tests using Jenkins CI server. It helps the team to be focused on development and not on running tests themselves. In case of any issues, the team is being alerted.
The next step is manual testing. The QA tester using test scenarios checks the system to make sure everything works properly from the business point of view. If something is not right, a bug is posted to Redmine and the developer needs to fix it. The QA flow repeats again!
When all the tests are passed, we are ready to deploy the application to production.