Testing at a Complex Project: QATestLab Real Case

Testing at a Complex Project: QATestLab Real Case
September 03 07:34 2019 Print This Article

While you are planning your vacation or are already enjoying a cocktail on the beach, the growth of IT projects is not going to slow down. They grow and develop, and often startups turn into huge companies with dozens of divisions. How then stay on top and maintain control over the quality of the product? Some companies handle quality assurance matters on their own, others, apply to a third-party QA.

How to achieve stable quality for a huge constantly developing project, at the same time maintaining its cost-effectiveness? Want to learn from the experience of a real project – read its brief summary on the QATestLab blog.

Why engage additional QA or what challenges it can solve

One of the most popular myths about a third-party QA is that independent provider only evaluates your application, and you get a list of errors, which doesn’t really help, right? Let’s see the real situations when projects apply for additional QA resources:

  • approaching release date + heavy working loads;
  • limited budget;
  • need for additional devices;
  • lack of QA competence.

Despite some general tendencies, every project has its specifics and reasons for engaging extra services on quality assurance. Let’s watch the example when QATestLab client, an international gambling company, applied to reach the following goals:

  1. Avoid law violations by checking the product for compliance with legal restrictions of the targeted regions.
  2. Ensure smooth transfer of the game to new servers.
  3. Optimize the budget via complementing in-house QA with an external team.

After the specification of project aims and requirements, a testing strategy is developed. As our experience shows, team interaction matters much as clients often worry about the communication flow. Here comes the next myth of poor interaction and weak control of the remote team activities. In this case, our specialists decided to form a team managed by a QA Lead for quick and effective communication. His main duties were task distribution, adjustment of the working load of QA engineers, and timely delivery of test results.

Do not hesitate to discuss the issues you are concerned about with the QA provider because everything may be far easier than you might think.

The scope of tasks to delegate to QA provider

Depending on the nature of the developed software and the state of affairs at a project, tasks for quality assurance may differ. To deal with the above-listed tasks and verify the quality of a game, our Client requested to check the following functionality:

what to test in a game

Functional testing

While performing this type of testing, QA engineers focus on the specifics of a product under testing. As the Client had a card game to test, special attention was paid to:

  • correct game operations;
  • random number generator (to ensure that cards are random and fair);
  • bonus accrual and currency calculation;
  • testing of game interruptions;
  • game rules evaluation (to verify that gameplay corresponds to the rules of the game);
  • collision detection and prevention mechanisms;
  • tournaments testing (single-player and multiplayer modes).

Sanity and Regression testing

Continuous development presupposes constant updates and fixes, and that’s why sanity and regression tests cannot be skipped. In the case we examine, the QATestlab team performed sanity testing after each game update. Full regression testing of desktop and mobile versions were conducted after hotfixes.

Regression tests are often connected with automation testing of a frequently used functionality. Auto scripts allow saving time and resources spent on testing. QATestLab engineers explored and analyzed logs generated after auto-script execution, thus gave support to the Client’s test automation department.

Test documentation support

Project documentation helps the testing team to understand project specifics, explore the developed software and its proper functioning. Test documentation, on the other hand, holds the results of work executed by the QA team: detected bugs with steps for their reproducing, recommendations on improvement, etc.

Test cases and checklists should be regularly updated and actualized due to the dynamic requirements of the project. This enabled the large team of our Client to take into account all recent developments and keep the releases of new versions stable.

Final word on engaging professional QA at a project

There is pretty much information on the Internet about third-party QA providers, pluses and minuses of such cooperation, possible difficulties, etc. However, a picture’s worth a thousand words and a real-life example can tell you much more. As for the case we addressed, QATestLab team assisted in the successful achievement of the set goals and continues the work with the Client constantly ensuring the quality of the product. Moreover, as a result of effective cooperation, QATestLab has been engaged at another Client’s project to perform functional testing of the human resource management system.

Related Posts:

About Article Author

view more articles
Emma Dallas
Emma Dallas

has 3-year experience in blogging, technical writing, and copywriting.

View More Articles


write a comment

No Comments Yet!

You can be the one to start a conversation.

Add a Comment

Your data will be safe! Your e-mail address will not be published. Also other data will not be shared with third person.
All fields are required.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.