Page History
...
For customers our advice is to use the agile testing quadrant to track make a testing strategy of which test you want to execute and which risks they mitigate.
In this paragraph we give an example about how this can be filled in from a customer point of view for Blueriq.
Keep in mind that every enviroment on a customer side has specific challenges.
Worked out the agile testing quadrants:
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 chances. Testing on the page modelling and exposed services | Checking to see if the Runtime is working correctly on the developed models | • 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 |
Performance (Q4) | Development team/ External expertise (Testters) | 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 |
...