Ongoing support, maintenance and monitoring

In this phase, QA engineers play the most important role – they determine that a certain problem actually does exist. Once the QA support receives an updated version with fixes, they re-test them to make sure that the bug is dead and gone. Finally, they run regression tests to check if other critical functionalities are still working perfectly. All these activities must be done very quickly, under time pressure, but with the utmost care.

As you can see, Quality Assurance maintenance is a really responsible and demanding position. Our QA engineers on a daily basis resolve a variety of cases. Firstly, they check whether an error was user-inflicted or maybe it was the software’s fault. In order to do that, they need to collect detailed feedback (what were the exact data, circumstances or actions that led to the problem occurring).

When QA support is 100% sure that the product is faulty, they cooperate with developers to fix it and re-test it as soon as possible. Without a quick response, you risk being swamped with negative comments of angry users who download and use the faulty version. Ongoing maintenance allows you to successfully fix any problems before they escalate and check areas exposed to constant changes in the code. Finally, the Quality Assurance team documents all specific cases in regression tests to future-proof your product from such problems.