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 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 |
...
Blueriq's flexibillity gives us the option to run the performance test on your enviroment, to use as an insight of your own enviroment 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 Blueriq and yor your online installation, then there is a big chance there are some hardware issues involved (server / network / client etc.). After doing this initial check it is always wise to create a performance test yourself with, for example, jmeterJMeter. This way you will know that the performance of your application is not decreasing with the introduction of new modelling or software changes.
Please be advised that we also have a page about modelling and performance, see also:Performance Tuning for more information about modelling in combination with performance.
...
Developing secure software is critical to a company’s reputation and bottom line. Blueriq customers feel the legal and financial pressure to assure the security of their (mission-critical) applications and have strong regulatory and privacy requirements to protect private data. Therefore security at Everest is treated at highest priority in the development of Blueriq. For are customers we have the following advice to introduce security checks in your agile development proces.
...
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 new code. For more information
Why did we choose READY API as our test automation tool ?
...
Overview
Content Tools