Page History
...
In most organization, the traditional testing pyramid is used , but it is used inverted inverted (see picture below). This is because most projects create a lot of tests on their user interface by using *Selenium for example (or any other automated framework). To make the feedback loop as short as possible it is advisable to change this inverted way of working so that the most tests are created as described in the testin pyramid in the previous paragraph. This will result in:
...
Using the test pyramid, you can draft a teststrategy against a standard setup of Blueriq. Which is made visible in the picture below.
Mapping a standard Blueriq and enviroment on the testing pyramid, gives the following insight:
- Studio should be tested with unit tests
- Runtime/ BAAS / Rest API should be tested with service and API layer tests
- Front-end (GU(GUI I) Interface) should be tested with User interface tests
...
Testing type | Possible Assignees | Targeting | Reasoning | Tool which can be used | Used at Blueriq |
|---|---|---|---|---|---|
Unit testing Model testing (Q1) | Business engineers and testers | All the new models | Ensuring that the model is correctly developed. According to standards | ||
API/ Logic/ Page models (Q2) | Business engineers and testers | Functionalities implemented in new stories/ past issues or bugs with high recurrence. Testing on the page modelling and exposed services | Checking to see if the Runtime is working correctly on the developed models, both functional and remaining logic which isn't tested in the unit/model layer. | • Cucumber • Selenium • Ranorex • Etc | •Ready API / Soap UI |
GUI testing (Q2) | Testers | The graphic interface and it’s logic, For example the view controller | Making sure no GUI related bugs are introduced when committing new code | • Testcafe • Other capure and playback tool | •Backstop JS |
| User testing (Q3) | Customer specific | The actual future user is testing the software. This to check the interaction between the users and the software. | Ensuring that the user has the correct interaction with the software and that the user can interact with the software | Manual interaction of the customer is needed. | Manual interaction with the users |
Performance (Q4) | Development team/ External expertise (Testers) | All the Blueriq components (Studio, Runtime, Publisher) | Verifying how Blueriq behaves when it comes to processing time and reliability | •Apache JMeter | |
Security (Q4) | Development team/ External expertise (Testers) | The Runtime and its relation to other third parties’ components. | Keeping and improving security standards for our application | • OWASP ZAP |
...
“Just as athletes can’t win without a sophisticated mixture of strategy, form, attitude, tactics, and speed, performance engineering requires a good collection of metrics and tools to deliver the desired business results.” — Todd DeCapua
The flexibility of the at Blueriq designed performance test gives the option to run the performance test on an environment where Blueriq is implemented. This can be used as an insight for the environment setup. By using the complete performance test project that Blueriq has developed, it is possible to test the IT enviroment of the deployed Blueriq application. If there are significant differences in the results between Blueriq and the specific installation, then there could be hardware issues involved (server / network / client etc.). After doing this initial check it is advised to create a performance test with, for example, JMeter in youw own enviroment. As an advice to our customers we strongly advise to include perfromance test from the beginning of the project, this way the performance can be monitored from the start and you can make lower the risks of not having an acceptable performancewhen introducing apllications with Blueriq.
...
Overview
Content Tools