Software Testing Foundation – Topic Cheat Sheet – ISTQB-ISEB
Here’s a mind map with the topics cheat sheet to prepare for the ISTQB-ISEB Software Testing foundation level exam.
You can download the image in A3 size if you want to print out and stick to the wall so you can visualise and try to memorize the topics.
Or you can use the mind map I have shared puclic and access using MindMeister with the free registration and look in more details.
Read Some Tips: ISTQB-ISEB Foundation Level Exam Preparation
Take a Quiz:ISTQB-ISEB Cetified Tester Foundation Level QUIZ
Download the High-Resolution image. (PNG format)
Download the A3 size to print in that size. (PDF format)
Download the High-Resolution image. (PNG format)
Download the A3 size to print in that size. (PDF format)
I have shared this mind map so you can copy and amend if you want to.
Create your own mind maps at MindMeister
Download the Mindmeister file. (.mind format – Zip file)
| Software Testing Foundation – ISTQB-ISEB Topics | ||
|---|---|---|
|
1. Fundamentals of Testing |
Why is Testing Necessary? | Human -> Error (mistake) -> Defect (fault, bug) which when executed may cause -> Failure Measures the quality of the software Gives confidence in the quality Reduces the overall level of risk How much testing? Depends on risk, safety & project constraints |
| Testing Objectives | Finding Defects Providing information for decision-making Preventing defects Gaining confidence about the level of quality |
|
| Testing Objectives | Finding Defects Providing information for decision-making Preventing defects Gaining confidence about the level of quality |
|
| Seven Testing Principles | Testing shows presence of defects Exhaustive testing is impossible Early testing Defect clustering Pesticide paradox Testing is context dependent Absence-of-error fallacy |
|
| Fundamental Test Process | Planning & Control Analysis & Design Implementation & Execution Evaluating Exit Criteria & Reporting Test Closure |
|
| The Psychology of Testing | Mindset of Developer & Tester Communication in a constructive manner Test Independence |
|
| Code of Ethics | Code is necessary, among other reasons, to ensure information accessed by testers are not put to inappropriate use. | |
|
2. Testing Throughout the Software Life Cycle |
Software Development Models |
Sequential Waterfall Iterative-Incremental Agile |
| Test Levels |
Black Box Functional Testing White Box Structural Testing Testing Related to Change Re-Testing |
|
| Maintenance Testing |
Triggered by Modification Change to deployed software system or its environment Extensive regression testing required |
|
|
3. Static Techniques |
Review Types | Informal Review Walk-through Technical Review Inspection |
| Activities of a Formal Review | Planning Kick-off Individual Preparation Review Meeting Rework Follow-up |
|
| Static Analysis by Tools |
Find defects in software source code and models Can locate defects that are hard to locate in dynamic testing |
|
|
4. Test Design Techniques |
Test Development Process | Test Design Specification Test Case Specification Test Procedure Specification |
| Specification-based or Black-box Techniques | Equivalence Partitioning Boundary Value Analysis Decision Tables State Transition Diagrams/Tables Use Case Testing |
|
| Structure-based or White-box Techniques |
Statement Testing & Coverage (weakest) Other Structure-based Techniques Condition Testing |
|
| Choosing Test techniques | Risk & Objectives Type of System & Dev Cycle Regulatory Standards Time & Budget Knowledge & Experience |
|
|
5. Test Management |
Test Organisation | Independent Testing Tasks of Test Leader & Tester |
| Test Planning & Estimation |
Test Planning Test Policy, Strategy Test Approaches Analytical Entry & Exit Criteria |
|
| Test Progress Monitoring & Control | Test Monitoring Test Reporting & Control Test Summary Report |
|
| Risks and Testing | Risk: Probability/Likelihood & Impact Project & Product Risks Risk-based testing approach |
|
| Configuration Management | Establish and maintain the integrity of the products and ensure all items of test-ware are identified, version controlled, tracked for changes, related to each other. | |
| Incident Management | Incident Management Incident Logging Test Incident Report |
|
|
6. Test Support for Testing |
Types if Test Tools | Management of Testing & Tests Performance & Monitoring Specific testing Needs Test Execution & Logging Test Specification Static Testing |
| Effective Use of Tools | Potential Benefits & Risks Special consideration for Test Execution, Static analysis & Test Management tools |
|
| Introducing a Tool into an Organisation | Main Considerations Start with a Pilot project Success factors for deployment |
Tools I’ve used to help with the video and mind mapping:
Mind Mapping – Mindmeister – Plan and brainstorm online with friends with the free mind mapping tool MindMeister http://www.mindmeister.com/?r=177956
Resources:
http://en.wikipedia.org/wiki/Software_test_documentation
http://www.computing.dcu.ie/~davids/courses/CA267/ieee829mtp.pdf
http://standards.ieee.org/findstds/standard/829-2008.html
http://www.ufjf.br/eduardo_barrere/files/2011/06/SQETestIncidentReportTemplate.pdf
http://www.geekinterview.com/question_details/46503
You must log in to post a comment.