Page History
...
“The definition of insanity is doing the same thing over and over again and expecting different outcomes.” – Einstein
TODO: HEADER FOR TABEL
Agile Testing Quadrant in spreadsheet
In the previous chapter is a visual image of the testing strategy, In this chapter we want give an example on how the Agile testing quadrant can be implemented (Who, Why and How ?).
The Q3 quadrant (business facing) we don't have a proposal, because this is always customer specific. In the table we also described which test tooling we use at Blueriq.+ korte introductie wat er met onderstaande tabel bedoeld wordt:
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 |
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 |
...
The OWASP Zed Attack Proxy (ZAP) is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers. It is used as a proxy to run selenium tests through and then ZAP can spider further throughout the complete application. ZAP will attack the application with the most popular (OWASP top10) attacks like injections, clickjacking, xss, csrf etc. ZAP should also run every night so you are sure that no important vulnerabilities are being introduced by the new code.
READY API
TODO: introduction what a ready API isFor more information, see: https://smartbear.com/
Why did we choose READY API as our test automation tool?
...
This can be of assistance to start with test automation projects.
Explanations
Wellicht een doorverwijzing naar pagina's op de community?
Selenium: todo
andere 'moeilijke termen'?
Overview
Content Tools