Page History

You can also view the webinar on my.blueriq.com: Webinar Blueriq Quality Assurance

...

The video and the use of the pyramid gives an indication about what to test on which level, on the points of speed and robustness. This to benifit the most of automated test on the correct level.

The testing pyramid and blueriq

What we still see lately is that In most organization the traditional testing pyramid is being used, but it is used inverted . So what we see is that a lot of (See picture below). This happens because most projects create a lot of tests on their user interface by using selenium for example (or any other automated framework). This should be changed so that the most tests are created as low as possible in the pyramid so that the feedback loop is as short as possible. This results in less scope change, less related code, less people involved etc. And this causes that bugs which are being found are cheaper to solve than when you will find them in the end of the lifecycle. This can be seen in the pictures below.

Image RemovedImage Removed

Image Added

This is described in the graph of Boehm, where the cost to fix will be greatly increased from testing and further in the proces. This supports the integration of early testing in the agile sprint teams and getting the most tests within development.

Image Added 

If we map the test pyramid on a standard blueriq setup,it would give this picture:

...