Page History
...
The latest webinar can be found on this Blueriq communitypage: Webinar Blueriq Quality Assurance
...
Customers will be the most important group of stakeholders for the majority of businesses, but also investors, employees, suppliers, and members of our wider society are stakeholders too. Delivering quality in an organization means knowing who the stakeholders are, understanding what their needs are and meeting those needs (or even better, exceeding expectations), both now and in the future.
This community page gives insights and ....
Testing Pyramid
“Quality is more important than quantity. One home run is much better than two doubles.” – Steve Jobs
The testing pyramid is often used in agile environments . The content and video about the use of the pyramid give an indication about what to test on which level. This to benefit the most of the automated test on the correct levelto setup a testing strategy. In this video (click to view) the quality pyramid is explained on a basic level, but also the advantages of using the tesing pyramid. At Blueriq we use this pyramid to setup up our automated test. This to benifit the most of automated tests.
http://www.agilenutshell.com/episodes/41-testing-pyramid
...
In most organization, the traditional testing pyramid is used, but it is used inverted (see picture below). This happens is because most projects create a lot of tests on their user interface by using *Selenium for example (or any other automated framework). To make the feedback loop as short as possible it is advisable to change this inverted way of working so that the most tests are created as low as possible described in the testin pyramid in the previous paragraph. This will result in:
- less scope change
- less related code
- fewer people involved and
- bugs which are found are cheaper to solve than at the end of the lifecycle
...
The graph of Boehm visually describes that the cost costs will exponential increase when testing further bugs are found in the processdevelopment proces. This supports the integration of early testing in the agile sprint teams and getting the most tests within development (In the scrum team).
If we map Using the test pyramid on , you can draft a teststrategy against a standard Blueriq setup, it would give this picture:
setup of Blueriq. Which is made visible in the picture below.
Mapping Blueriq and the testing pyramid, gives the following:
- Studio should be tested with unit tests
- Runtime/ BAAS / Rest API should be tested with service and API layer tests
- Front-end (GUI Interface) should be tested with User interface tests
In this combined model of Blueriq and the testing pyramid In this model most of the tests are on the lowest level , the resulting benefits are, as mentioned beforeof the pyramid. This will result in the following benefits:
- Cost to develop and maintain automated test is up-to-par
- Execution time on automated tests will be optimal
- Possibility of false negatives is decreased
- Increase in coverage closest to the team
...
For 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
The links in the colums 'Tools which can be used' and 'Used at Blueriq' are clickable for more information on the given testing tools.
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 |
| 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 |
...
“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
The flexibility in Blueriq of the designed performance test gives the option to run the performance test on an environment where Blueriq is implemented. This can be used as an insight for the environment setup. By using the complete performance test project that Blueriq supplieshas developed, it is possible to test the landscape that the application will run inIT enviroment of the deployed Blueriq application. If there are significant differences in the results between Blueriq and the specific installation, there is a big chance some hardware issues are then there could be hardware issues involved (server / network / client etc.). After doing this initial check it is advised to create a performance test with, for example, JMeter in youw own enviroment . This way the performance can be monitored of the performance of the application and make sure it stays acceptable when introducing new features with Blueriq.
Performance information:
...
Overview
Content Tools