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 parts of the syllabus which I believe will aid you to memorize 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, the more you understand 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 useful too to help you with the exam.
Hope you like it. Feel free to drop me a comment, or inform anything that I’ve missed here. Good luck.
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.
A software design model where the stages are ongoing, unlike the waterfall method. Testing occurs as part of each sprint.
- Tests individual units or pieces of code for a system.
- V-model document: program specification.
- Performed to ensure that two modules operate together correctly.
- V-model document: technical specification.
- 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.
- To determine whether the product indeed satisfies its specifications and user story requirements.
- V-model document: requirement specification.
Tests that verify a specific action or function of the code.
Testing of a software application for its non-functional requirements (i.e. the quality attributes of the system).