istqb software testing

Software testing topics highlighted in the ISTQB include:

• Basics, terms, principles
• The test process (planning, monitoring & control, analysis, design, realization, execution, completion)
• Test design process
• Test specification methods/test design procedures

(Black box test design method: Equivalence partitioning, boundary value analysis, decision table testing, condition-based test, use case-based test; 

White-box test design procedures: statement, decision and condition coverage).

• Dynamic and static test techniques (static analysis, reviews)
• Realize, execute and evaluate tests
• Testing in the software lifecycle (test types, test levels, e.g. module/component testing, integration testing, system testing, acceptance testing)
• Plan, prioritize and control tests
• Setting up test teams, roles, qualifications
• Test automation and tools
• mobile testing
• embedded testing
• security testing

Some particularly important terms that ISTQB testers should also be familiar with are:

A systematic testing strategy (e.g. risk-based testing or specification-based testing) should consider the following aspects:

1. functionality of the software (correctness, completeness, appropriateness)

2. reliability (maturity, fault tolerance, reproducibility)

3. usability (understandability, learnability)

4. performance efficiency (performance, load, stress):

5. maintainability (how easily the software can be modified without limiting stability and testability, including compliance to coding guidelines and complexity metrics).

6. portability (how easily the software can be ported to another system, browser, operating system, data base, but also organizational portability)

7. security (authenticity, protection of data against unauthorized access, e.g. through data encryption)

8. compatibility (interoperability: how compatible is the software in processing data with and from other systems?; co-existence: systems do not negatively affect each other, e.g. resource conflicts).

The test strategy is used to create targeted test cases that adhere to and support specific criteria of the software under test. Based on the requirements of the system to be tested, the necessary test procedures are designed and the test data is compiled. Existing test plans and test specifications are reviewed, e.g. to increase test coverage.

The Syllabus teaches common test techniques, such as:

• Black-box test design techniques: 
  • Equivalence partitioning, 
  • Boundary value analysis, 
  • Decision table testing, 
  • State-based testing, 
  • Use case based testing; 
• White-box test design techniques (Statement, Decision and Condition coverage), 
• Exploratory testing
• Requirements based testing
• Business process based testing
• Static testing like reviews/inspections, code analysis

Test management creates a cost-effective test strategy that plans the test effort along quality objectives, product and project risks. The test manager is responsible for controlling the test activities, coaching the test team, implementing the test plan effectively and efficiently, creating test and defect reports, and objectively evaluating the quality and release maturity of the product, because this information is an important contribution to the go-live decision by management. 

The automation of software tests should replace time-consuming manual testing and sustainably increase test efficiency: Accelerated execution, unlimited re-runnability and independence from test personnel are the benefits sought by this approach, for example in the case of frequently repeated regression tests. The right automation architecture helps to avoid high testing effort, high customization costs, lack of robustness and lack of transparency as well as wrong tooling decisions and high maintenance effort.

A test type is focused on a specific test objective, such as reliability testing, regression testing, usability testing. The test type may also refer to one or more test levels or phases. Some examples taught by the ISTQB standard are:

• Functional testing
• Non-functional testing
• Load and performance testing
• Internationalization testing
• Localization testing
• Compatibility testing
• Security testing
• Usability testing
• Documentation testing

Mobile first has arrived in software development - cell phones and tablets are already the main device for many users for private, on business trips or in the home office also for professional research and collaborative activities. Clear structures, intuitive usability, unlimited functionality, fast response times, low use of storage capacity, and energy efficiency are just a few of the keywords that have priority here. Given the diversity of end devices and platforms, a large number of different combinatorial scenarios arise, which pose major challenges for software quality assurance and software testing. trendig has a Mobile App Testlab ready for this purpose and has co-written a book on the subject in German language: Basiswissen Mobile App Testing ISBN 978-3-86490-748-7.