Testing Throughout the Software Life Cycle – Chapter 2 – ISTQB Foundation

All information to help with the ISTQB exam to obtain foundation-level certification is valid. This is the second part of a series of short pieces of the syllabus, which I believe will aid you in memorizing what is very likely to be on the questions. (If you missed Chapter 1, you can access it here)

Read, then practice the exam for chapter 2 – Testing Throughout the Software Life Cycle; link at the end of this summary, practice the quiz as much as you like or until you feel comfortable enough to go to the next chapter.

If you feel that you are ok to try the actual exam, there’s a quiz for that as well next to chapter two.

The more you read, the more you understand, and the more you know more you are ready to take the exam.

I have uploaded a mind map with a graphical visualization of the ISTQB Foundation Level topics, a kind of Cheat Cheat; you may find it helpful too to help you with the exam.

I hope you like it. Feel free to drop me a comment, or inform anything that I’ve missed here. Good luck.

ISTQB Cheat Cheat | Chapter 2 Practice Exam Quiz | ISTQB Foundation Level Quiz

Want to Watch the Newer ISTQB 2018 Version?

Waterfall model

Life cycle through which a project goes—sequential or linear design process. Testing is carried out at the end.


The methodology that pays more attention to testing. The development process proceeds down the left-hand slope of the V, defining requirements and designing system components. At the base of the V, the code is written. On the upward-sloping right side of the model, testing of components, integration testing, and acceptance testing are performed.

Iterative model

Unlike the waterfall method, a software design model where the stages are ongoing. Testing occurs as part of each sprint.

Unit testing

  • Tests individual units or pieces of code for a system.
  • V-model document: program specification.

Integration testing

  • They are performed to ensure that the two modules operate together correctly.
  • V-model document: technical specification.

System testing

  • Tests the various parts of the applications work together within a system work.
  • Non-functional requirements for system testing may be load handling, reliability, installability, etc.
  • V-model document: functional specification.

Acceptance testing

  • To determine whether the product indeed satisfies its specifications and user story requirements.
  • V-model document: requirement specification.

Functional testing

Tests that verify a specific action or function of the code.

Non-functional testing

We are testing a software application for its non-functional requirements (i.e. the system’s quality attributes).

Structural testing

Testing considers the internal mechanism [structure] of a system or component. Types include branch testing, path testing, and statement testing.

ISTQB Cheat Cheat | Chapter 2 Practice Exam Quiz | ISTQB Foundation Level Quiz

Want to Watch the Newer ISTQB 2018 Version?


  • Rogerio da Silva

    Rogerio da Silva is a Brazilian who lives in the UK for a little over two decades. He is the owner of a test consulting and outsources services for software development. He likes to blog, write and create content that teaches others how to live a better life.  He loves reading biographies of successful authors and dream builders because they inspire him to keep creating!
    You can contact Rogerio for anything related to Business & Test Analyst | Microsoft Dynamics 365 CRM | QA | Agile | Manual | Integration & Automation | DevOps | API | Cloud | AI | IoT | CRM | Website Consulting | Email Consulting | Facebook Ads | Social Media Marketing Plan | Sales Funnel | Looking for Scalable Services? InShore, OffShore or Hybrid. Interested? Ask me how we can help.

Leave a reply


Now available on amazon prime

eBook (Amazon)

The Testers Book - An Unconventional Way to Software Testing - Revised Edition

Paperback (Lulu.com)