Page History
...
In this model most of the test tests are on the lowest level, the benifits which this will give resulting benefits are:
- Cost to develop and maintain automated test is up-to-par
- Execution times time on automated tests will will be optimal
- Possibillity Possibility of false negatives is decreased
- Increase in coverage closest to the team
...
For customers our advice is to use the agile testing quadrant to make a testing strategy of which test type of tests you want to execute and which risks they mitigate.
In this paragraph we give an example about show how this can be filled in implemented for Blueriq from a customer point of view for Blueriq.
Keep in mind that every enviroment on a customer side has IT landscape has its own specific challenges.
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 the new models | Ensuring that the Model 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, 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 |
...
With the introduction of Blueriq 9.9 performance test tests are introduced with Blueriq, for more information on this topic, see: Performance reports
The flexibility in Blueriq 's flexibillity gives us the option to run the performance test on your enviromentenvironment, to use as an insight of for your own enviroment environment setup. By using the complete test project that Blueriq supplies, it is possible to test the landscape that your application will run in. If there are significant differences in the results from between Blueriq and your online specific installation, then there is a big chance there are some hardware issues are involved (server / network / client etc.). After doing this initial check it is always wise advised to create a performance test yourself with, for example, JMeter. This way you will know that can monitor the performance of your application is not decreasing with the introduction of new modelling or software changesand make sure it stays acceptable when introducing new features.
Please be advised that we also have a page section in our documentation about modelling and performance, see also:Performance Tuning for more information about modelling in combination with performance.
For more information about these services please contact our support desk.
...
Overview
Content Tools