Re-occurrence of errors and mistakes after some code changes is a very frequent problem that wastes time and nerves of any developer. Such errors could be critical and sometimes lead to serious problems in a product. Because of this regression testing is the most important thing in quality assurance of any software product. But what should testers do when they need to look after a highly loaded system with a huge amount of inputs and varied functionality?
Parallel testing (Prod Parallel) is an approach in which a new version of a system works simultaneously with a release version and it gets the same data to the input that prod has. This approach helps when a software product has a varied functionality, but the QA team is extremely small. It saves QA resources, helps to monitor mostly all changes and makes a big part of regression testing.
In this talk, you'll find out how to create a testing process with a Prod Parallel version and what advantages and disadvantages it has. The author will tell about his own experience of such testing and will use his testing of one trading platform component as an example.
This talk can be interesting for both manual testers and QA Automation Engineers.
Andrey is currently working at Deutsche Bank in QA team. Among his responsibilities is the development of a highly loaded Unix-hosted system for trading. Andrey graduated from Lomonosov Moscow State University with MA Equivalent degree. Previously worked at Intel in a team that developed compilers, took part in test framework development and tested Intel C/C++ and open source Clang compilers. Is interested in development, tests automation and creation of tools for SDLC.