Our dedication to delivering quality work has led us to implement multiple testing phases through which we submit every site or product that has been developed. The testing begins with the development team and is then passed on to the QA team for further validation.
- First, developers implement functional tests as they go in order to constantly check if new changes are compatible with previously implemented features.
- Larger features are given unit test coverage so that tests run fast and test only the needed functionality. This helps the developers pinpoint problems and fix them quickly.
- Project teams rely on continuous integration to ensure that there is no bug in the code that is committed: tests are automated to run at every commit, thus warning developers of any bug before a release.
Once the code is committed and released to our testing environment, it is reviewed by our quality assurance (QA) team to make sure that the products meet all the project requirements:
- QA analysts run acceptance testing to ensure the testability of every release.
- QA analysts run regression testing of every release to check the previously implemented features.
- QA analysts check all the new features that have been released, individually and manually.
- QA analysts perform load testing to control the site's performance.