Feedback

  • Name *

  • Company

  • Email *

  • IM (Skype)

  • Message *

  • captcha

Thank you for contacting us !

Quality Assurance

qa-iconApplications must be thoroughly checked technically before placing them into production, because businesses can’t afford downtime but meanwhile application should move forward by adding new features without making any side effect to the existing ones. That means continuous integration (CI) and that is where Optimum-web has a great experience.

All starts from the beginning of the implementation process when technical specification is ready. Features are split into sprints ( planned 2-3 week periods with a list of features ). At that stage QA person makes test scenarios for manual testing based on the specification and use them when developers complete sprint. That ensures that we will not miss anything to test and that is one level of testing.

While coding programmers are writing unit and functional automated tests to make sure we can check code side of the project when new features are added and that is another level of testing.

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 and aware the team about any problem appeared while testing. All that Jenkins is doing.

If that step is passed – manual testing begins. QA tester using test scenarios checks the system to make sure all is working as should from business point of view. If something is not right a bug is posted to Redmine and developer will fix it and the QA flow will be repeated again.

When all tests are passed we are ready to update application in production.