Page History
...
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 modeling and exposed services | Checking to see if the Runtime is working correctly on the developed models, both functional and remaining logic which is not tested in the unit/model layer. | • Cucumber • Selenium • Ranorex • Etc | •Ready API / Soap UI |
GUI testing (Q2) | Testers | The graphic interface and its logic, For example, the view controller | Making sure no GUI related bugs are introduced when committing new code | • Testcafe • Other capture 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 |
...
Overview
Content Tools