Page History

...

The latest webinar can be found on this page: Webinar Blueriq Quality Assurance (Will be published soon)

What is quality?

“Quality is not an act. It is a habit.” – Aristotle

...

^{http://www.agilenutshell.com/episodes/41-testing-pyramid}

The testing pyramid and Blueriq

In most organization, the testing pyramid is used inverted (see picture below). This 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 described in the testing 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

Boehm's law

The graph of Boehm visually describes that costs will exponential increase when bugs are found in the development process. This supports the integration of early testing in the agile sprint teams and getting the most tests within the development (in the scrum team).

...

• 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
  
  

Agile test quadrants

For customers, our advice is to use the agile testing quadrant to make a testing strategy of which type of tests you want to execute and which risks they mitigate. In this paragraph, we show how this can be implemented for Blueriq from a customer point of view. Keep in mind that every IT landscape has its own specific challenges. 

...

“The definition of insanity is doing the same thing over and over again and expecting different outcomes.” – Einstein

Agile Testing Quadrant in spreadsheet

In the previous chapter is a visual image of the testing strategy. In this chapter we want to give an example on how the Agile testing quadrant can be implemented (Who, Why and How ?).

...

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

The at Blueriq 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 has developed, it is possible to test the IT environment of the deployed Blueriq application. If there are significant differences in the results between Blueriq and the specific installation, 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 your own environment.  As an advice to our customers, we strongly advise to include performance test from the beginning of the project, this way the performance can be monitored from the start and you can make lower the risks of not having an acceptable performance when introducing applications with Blueriq.

Performance information:

Performance tests are introduced from Blueriq 9.9: Performance reports 

...

To introduce the security checks in an agile development process the following advice needs to be taken into consideration:

Penetration test

Keep in mind that it's advisable that a penetration test will always be advised on a production environment before your Blueriq application goes live

OWASP Dependency Checker

Dependency-Check is a utility that identifies project dependencies and checks if there are any known, publicly disclosed, vulnerabilities in 3rd party components. This dependency checker is integrated into our Jenkins CI server. Currently Java and .NET are supported. The OWASP Dependency-check is used to scan our dependent libraries to identify any known vulnerable components. The core engine contains a series of analyzers that inspect the dependencies, collect pieces of information about the dependencies (referred to as evidence within the tool). The evidence is then used to identify the Common Platform Enumeration (CPE) for the given dependency. If a CPE is identified, a listing of associated Common Vulnerability and Exposure (CVE) entries are listed in a report.

Dependency-Check updates using the NVD Data Feeds. For more information about the dependency, checker see: OWASP dependency plugin (Jenkins). The standard libraries with Blueriq are checked this way. When using extra libraries, it would be advisable to run tool also over the extra libraries.

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 the new code.

READY API

For more information, see: https://smartbear.com/

Why did we choose READY API as our test automation tool?

• Non technical interface
• JDBC connections
• Composite projects with GIT integration
• Dynamic environments
• Reusable test cases (Libraries)
• Data driven testing
• CI (Jenkins) integration

Ready API examples

Soon we will place here a SOAP UI Project and a studio project. 

...