Blog entry by OZZY SECIO RIZA 5116201030

Picture of OZZY SECIO RIZA 5116201030
by OZZY SECIO RIZA 5116201030 - Thursday, 22 December 2016, 5:43 PM
Anyone in the world

Back-to-Back testing ensures that two different instances of an implementation have the same structural behavior. A typical use case in a model-based development process is comparing the model (MIL) which is considered to be an “executable specification” against the production code (SIL).

backToback.PNG

 

Scenario of Back-to-Back Testing

  1. The aim of testing is defined. Test cases are designed.
  2. The checking is performed with the usage of test cases. Specialists launch applications or systems and record the results of their work.
  3. Obtained results are automatically compared.
  4. Testers make the difference report that contains the results of comparison.

 

There can be some misinterpretations of the notion ‘the difference report’. Actually, everything is very simple. The difference report contains necessary data to demonstrate the problems that may happen among the various system versions.

Here is one more explanation of back-to-back testing. This checking type is executed in the presence of two identical transformers. One of these transformers remains open and the other one – loaded.

It is cheaper to perform back-to-back testing when the system or application have some modifications. There is no need to execute usability testing or performance testing one more time. Tester may just compare the work of system versions.

In other words, back-to-back testing is more effective during mobile application testing and website testing.

 

Reference

http://blog.qatestlab.com/2015/11/10/back-back-testing/

Associated Course: KI142303BKI142303B