Page History
...
The testing pyramid is often used in agile enviroments, for more information see this video: http://www.agilenutshell.com/episodes/41-testing-pyramid
This level gives indication about what to test on which level, on the points of speed and robustness
The testing pyramid and blueriq
...
“The definition of insanity is doing the same thing over and over again and expecting different outcomes.” – Einstein
For customers our advice is to use the agile testing quadrant to track which test you want to execute. 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 |
•Studio Unit tests
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 |
•SoapUI NG
•Cucumber
•Jmeter
•Telerik
•Selenium
•Ranorex
•Etc
• 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 |
•Selenium web driver
•Testcafé
•Nightwatch
• 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 |
•Jmeter
•Load UI
| •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 |
•Burp suite
| • OWASP ZAP |
Performance
“Just as athletes can’t win without a sophisticated mixture of strategy, form, attitude, tactics, and speed, performance engineering requires a good collection of metrics and tools to deliver the desired business results.”— Todd DeCapua
With the introduction of Blueriq 9.9 performance test are introduced with Blueriq, for more information on this topic, see: https://my.blueriq.com/display/DOC/Performance+ReportsPerformance reports
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 on locationyor 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, jmeter. This way you will know that the performance of your application is not decreasingwith decreasing with the introduction of new code. modelling.
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.
For more information about this service these services please contact our service support desk.Security
Security
“Testing is an infinite process of comparing the invisible to the ambiguous in order to avoid the unthinkable happening to the anonymous.”— James Bach
...
Dependency-check updates using the NVD Data Feeds. For more information about the dependency checker see: https://wiki.jenkins.io/display/JENKINS/OWASP+Dependency-Check+PluginOWASP dependency plugin (Jenkins). The standard libraries with Blueriq are checked this way. If you use extra libraries or replace our libraries, it would be advisable to run this on your enviroment.
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 new code. For more information
...
Overview
Content Tools