ISTQB Foundation Level and Agile Tester Certification guide

This site has free and premium study material / guide needed to pass the ‘ISTQB Foundation Level Certification’ and the newly introduced ‘Agile Tester Extension Certification’.

International Software Testing Qualifications Board (ISTQB) is an international organization that offers globally recognized certifications in software testing. Having a certification establishes credibility of the candidate. This site also contains everything you will need for a software testing tutorial. Two of the most popular certifications are below:

ISTQB Foundation Level Certification study guide

Foundation Level Certification is aimed at candidates who have recently completed their education and want to take up software testing as a profession. It is also taken up by experienced candidates who want to demonstrate their practical knowledge of software testing. It is the most popular certification course recognized by organizations worldwide. It provides software tester a basic understanding of the fundamentals of software testing along with processes, tools, techniques and management methodology. Launch the study guide >>

ISTQB Agile Testing Certification study guide

Agile Tester Extension Certification is beneficial for testers who are already working on Agile methodology and also for those who wish to learn it.  Testers in Agile project have different approach of testing when compared to traditional projects. Testers should have a very clear understanding of the values, principles, processes and tools used in testing Agile projects. This certification guide provides the tester with an easy-to-understand explanation of the topics covered in the Agile Tester certification. Launch the study guide >>

What is the ISTQB Agile Tester Extension Certification?

ISTQB Agile Tester Extension Certification
ISTQB has introduced a new certification known as ISTQB Agile Tester Certification Extension. Software development and testing in an agile project follows a significantly different approach compared to regular software projects. Testers who are part of the agile projects need to have a good understanding of the Agile software development processes, the testing methodologies, difference in testing between traditional and agile approaches, tool and techniques in Agile project etc. This certification tests the knowledge of candidates in these areas. [Read more…]

ISTQB Foundation Level Certification – The Definitive Guide

ISTQB Certification is an internationally recognized software testing certification which is an essential part of QA Trainings in many organizations. ISTQB certification is also important for candidates looking for a job as a Software Tester. This site contains everything you need to know about the ISTQB exam including the study material / study guide you need in order to successfully pass the ISTQB Foundation Level exam. You can go through each topic in a sequence by clicking the “<< Previous Topic” and  “Next Topic >>” links at the top and bottom of the page.

ISTQB has 3 levels of certification – Foundation Level, Advanced Level and Expert Level.

There is no educational or other pre-requisite for taking the Foundation Level exam. ISTQB recommends candidates to have 6 months of work experience before they take up the certification but this is not a requirement.

Launch the ISTQB Foundation Level study material >>


Check out the links below for more details regarding ISTQB:

ISTQB Certification SyllabusIf you are preparing for the ISTQB exam, you can follow the links in the menu  titled “ISTQB Certification Exam Study Material” or choose a category below to go through each topic in that knowledge area.

If you find this site useful, please share our links with your friends.

Posts not related to the ISTQB certification can be found under the category Software Testing


The ISTQB Certification syllabus for Foundation Level comprises of the following categories of knowledge areas that are part of the exam:

Attention ISTQB aspirants!!!
Most candidates who fail ISTQB fail by less than 10 marks
Are you struggling to study for ISTQB Foundation Level Exam?
Are you looking for the latest premium question papers?
Do you wish there was concise study material for the ISTQB Exam? presents
100% Sure Pass - Premium ISTQB Foundation Exam Study Material 2016

The Premium Study Material contains the following:
1. The best book to prepare for ISTQB Foundation Level CTFL Exam
2. Premium question dumps from recent exams
3. Glossary of all the terms used in ISTQB Foundation Level
4. Step by step guide and 4 other bonuses that will help you pass the exam with high score

Stop struggling and pass with high score. Click here to find out more

What is Software Testing Life Cycle (STLC)?

Just like developers follow the Software Development Life Cycle (SDLC) likewise testers also follow the Software Testing Life Cycle which is called as STLC. It is the sequence of activities carried out by the testing team from the beginning of the project till the end of the project.

Software Testing Life Cycle is a testing process which is executed in a sequence, in order to meet the quality goals. It is not a single activity but it consists of many different activities which are executed to achieve a good quality product. There are different phases in STLC which are given below:

  1. Requirement analysis
  2. Test Planning
  3. Test case development
  4. Environment Setup
  5. Test Execution
  6. Test Cycle Closure

Software testing life cycle (STLC)Each of the step mentioned above has some Entry Criteria (it is a minimum set of conditions that should be met before starting the software testing) as well as Exit Criteria (it is a minimum set of conditions that should be completed in order to stop the software testing) on the basis of which it can be decided whether we can move to the next phase of Testing Life cycle or not.

Let us discuss about each phase in detail:

Requirement Analysis

This is the very first phase of Software testing Life cycle (STLC). In this phase testing team goes through the Requirement document with both Functional and non-functional details in order to identify the testable requirements.

In case of any confusion the QA team may setup a meeting with the clients and the stakeholders (Technical Leads, Business Analyst, System Architects and Client etc.) in order to clarify their doubts.

Once the QA team is clear with the requirements they will document the acceptance Criteria and get it approved by the Customers.

Activities to be done in Requirement analysis phase are given below:

  • Analyzing the System Requirement specifications from the testing point of view
  • Preparation of RTM that is Requirement Traceability Matrix
  • Identifying the testing techniques and testing types
  • Prioritizing the feature which need focused testing
  • Analyzing the Automation feasibility
  • Identifying the details about the testing environment where actual testing will be done

Deliverables (Outcome) of Requirement analysis phase are:

  • Requirement Traceability Matrix (RTM)
  • Automation feasibility report

Test Planning

Test Planning phase starts soon after the completion of the Requirement Analysis phase. In this phase the QA manager or QA Lead will prepare the Test Plan and Test strategy documents. As per these documents they will also come up with the testing effort estimations.

Activities to be done in Test Planning phase are given below:

  • Estimation of testing effort
  • Selection of Testing Approach
  • Preparation of Test Plan, Test strategy documents
  • Resource planning and assigning roles and responsibility to them
  • Selection of Testing tool

Deliverables (Outcome) of Test Planning phase are:

  • Test Plan document
  • Test Strategy document
  • Best suited Testing Approach
  • Number of Resources, skill required and their roles and responsibilities
  • Testing tool to be used

Test Case Development

In this phase the QA team write test cases. They also write scripts for automation if required. Verification of both the test cases and test scripts are done by peers. Creation of Test Data is done in this phase.

Activities to be done in Test Case Development phase are given below:

  • Creation of test cases
  • Creation of test scripts if required
  • Verification of test cases and automation scripts
  • Creation of Test Data in testing environment

Deliverables (Outcome) of Test Case Development phase are:

  • Test cases
  • Test scripts (for automation if required)
  • Test Data

Test Environment setup

This phase includes the setup or installation process of software and hardware which is required for testing the application. In this phase the integration of the third party application is also carried out if required in the project.

After setting up the required software and hardware the installation of build is tested. Once the installation of build is successful and complete then the Test Data is generated.

After the creation of Test data the Smoke testing is executed on the build in order to check whether the basic functionalities are working fine or not. This phase can be done in parallel with the Test Case Development phase.

Activities to be done in Test Environment Setup phase are given below:

  • As per the Requirement and Architecture document the list of required software and hardware is prepared
  • Setting up of test environment
  • Creation of test data
  • Installation of build and execution of Smoke testing on it

Deliverables (Outcome) of Test Environment Setup phase are:

  • Test Environment setup is ready
  • Test Data is created
  • Results of Smoke testing

Test Execution

Before starting the Test Execution phase the Test Environment setup should be ready. In Test Execution phase the test cases are executed in the testing environment.

While execution of the test cases the QA team may find bugs which will be reported against that test case. This bug is fixed by the developer and is retested by the QA.

Activities to be done in Test Execution phase are given below:

  • Execution of Test Cases
  • Reporting test results
  • Logging defects for the failed test cases
  • Verification and retesting of the defect
  • Closure of defects

Deliverables (Outcome) of Test Execution phase are:

  • Test execution Report
  • Updated test cases with results
  • Bug Report

Test Cycle Closure

In order to start the Test Cycle Closure activity the Test Execution phase should be completed. In Test Cycle phase the QA team will meet and discuss about the testing artifacts.

The whole intent of this discussion is to learn lessons from the bad practices. This will help in future projects.

Activities to be done in Test Cycle Closure phase are given below:

  • To evaluate the test completion on the basis of Test Coverage and Software Quality
  • Documentation of the learning from the project
  • Analyzing the test results to find out the distribution of severe defects
  • Test Closure Report preparation

Deliverables (Outcome) of Test Cycle Closure phase are:

  • Report of Test Closure

The below table briefly explains the Software Testing Life Cycle along with the Entry Criteria, Activity, Exit Criteria and Deliverable associated with each phase:

STLC phases Entry Criteria Activity Exit Criteria Deliverables (Outcome)
Requirement analysis Availability of Requirement document both Functional as well as non-functional

Architectural document of the application or the product should be available

Acceptance criteria defined and duly signed by the customers


Analysis of System Requirement specifications to understand the different business modules and it’s functionalities

To identify the user profile, user interface and user authentication

Types of tests to be performed on the application or product should be identified

Should collect the details about testing priorities

Preparation of RTM that is Requirement Traceability Matrix

Test Environment details should be identified in order to do testing

Analysis of automation possibility if it is required

RTM should be signed off

The customer should sign off on the test automation feasibility

Requirement Traceability Matrix (RTM)

Report on Automation Feasibility if it is applicable

Test Planning Detailed requirement document

Requirement Traceability Matrix (RTM)

Automation Feasibility Report


Preparation of Test Plan document

Preparation of Test strategy document

To analyze the best suited testing approach for the application or product

To analyze the testing techniques and the types of testing to be carried out in order to maintain the quality

Selection of the testing tool

Estimation on the testing efforts

Resource planning as per the skill required for testing and also assigning roles and responsibility to them

Approved Test Plan document

Approved Test Strategy document

Document of Effort estimation

Test Plan document

Test Strategy document

Effort estimation document

Test case development Detailed Requirement document

Test Plan and Test strategy documents

Automation Feasibility Report



Creation of test cases for all the modules or features in the application or product

Creation of automation scripts if required

Review of test cases and test automation scripts

Test data creation

Reviewed Test cases

Reviewed Test automation scripts

Test data creation ready for testing


Test cases

Test automation scripts

Test data

Test Environment setup System design documents should be available

Architectural document of the application should be available

Environment set-up plan document should be available


Understanding the design and architecture of the application

Setting up the test environment

Installation of required hardware and software in order to start testing the application

Integration of any third party application (if required)

Installation of build

Creation of test data

Execution of smoke testing on the build

Accepting or rejecting the build as per the smoke test result

Environment setup is ready for testing

All the required software and hardware are installed

Build installation is complete and successful

Test data creation is complete

Smoke testing is done

Test environment along with test data

Smoke test result

Test Execution Documents like RTM, Test Plan, Test strategy, Test cases and Test scripts should be ready

Test environment should be ready

Test data should be ready

Integration of third party application (if required) should be successful

Smoke testing of the application should be successful


Execution of test cases

Preparation of test result document

Logging defects for the failed test cases

Mapping of defects with the test cases

To update the test cases and test strategy if required

Fixed defects should be retested

Closure of the defects if they are working as expected

Execution of regression testing of the application or product in order to ensure its stability post defect closure


All test cases are executed

Defects are logged and tracked for closure

Completed the test case execution

Updated the test cases wherever required

Defects reported

Test cycle closure All the test cases are executed and updated

Test results are documented

Defect logs are available

Evaluation of the test completion on the basis of Test Coverage and Software Quality

Preparation of Test Closure report

Analyzing the test results to find out the distribution of severe defects

Signed off Test Closure report by the client


Test closure Report

What is Monkey testing? Types, Advantages and Disadvantages

Monkey testing is a technique used in software testing to test the application or product by providing random data and observing if the system or application crashes.

  • In Monkey testing the tester or sometimes developer also is considered like a monkey assuming that if a monkey uses the computer then he will enter some random data without any knowledge or understanding.
  • Here the tests done are very random and it may not be correct.
  • Because of such random testing the testers may not be able to recreate the issues or bugs.What is Monkey Testing?

Advantages of Monkey testing:

  • Monkey testing is a very good approach to find out some new bugs which may not be possible from the stated scenarios.
  • Monkey testing can also be a good way to perform stress testing and load testing since the scenarios tested are generally random and ad-hoc.
  • It is very easy to execute because it just requires some random data to run against some random tests.
  • Execution of test cases and setting up of environments expenses are very less in monkey testing.
  • By using tools the process of Monkey testing can be automated.
  • Monkey testing can be performed for desktop applications, web applications as well as mobile applications.

Disadvantages of Monkey testing:

  • The test carried out during monkey testing is so random that it is either not possible or very difficult to recreate any bug.
  • It’s very difficult and time consuming to analyze the unexpected issues found during the monkey testing.
  • Testers have difficulty in defining the exact test scenarios and they also cannot assure the accuracy of test cases.
  • Monkey testing may consume lots of time before finding a bug because it does not have any predefined tests.

Types of Monkey testing

There are three types of Monkey testing:

Dumb monkey tests: In Dumb monkey tests the testers have no knowledge of the product or application. They do not have any idea about their inputs whether it’s valid or invalid. They are also known as ‘Ignorant monkeys’.

Smart monkey tests: In Smart monkey tests the testers have a good idea of the system or application. They know exactly the product’s functionality. They provide the valid inputs to perform testing.

Brilliant monkey tests: In Brilliant monkey tests the testers have fair idea as how the users are using the product and they carry out their testing with the user’s perspective.

What is smoke testing? When to use it? Advantages and Disadvantages

Smoke testing is a type of software testing which ensures that the major functionalities of the application are working fine. This testing is also known as ‘Build Verification testing’. It is a non-exhaustive testing with very limited test cases to ensure that the important features are working fine and we are good to proceed with the detailed testing.

The term ‘smoke’ testing is originated from the hardware testing, where a device when first switched on is tested for the smoke or fire from its components. This ensures that the hardware’s basic components are working fine and no serious failures are found.

Similarly, when we do smoke testing of an application then this means that we are trying to ensure that there should NOT be any major failures before giving the build for exhaustive testing.

  • The purpose of the smoke testing is to ensure that the critical functionalities of an application are working fine.
  • This is a non-exhaustive testing with very limited number of test cases.
  • It is also known as Build verification testing where the build is verified by testing the important features of the application and then declaring it as good to go for further detailed testing.
  • Smoke testing can be done by developers before releasing the build to the testers and post this it is also tested by the testing team to ensure that the build is stable enough to perform the detailed testing.
  • Usually smoke testing is performed with positive scenarios and with valid data.
  • It is a type of shallow and wide testing because it covers all the basic and important functionalities of an application.
  • Usually the smoke testing is documented.
  • Smoke testing is like a normal health check up of the build of an application.

Examples for Smoke Testing

Let us assume that there is an application like ‘Student Network’ which has 15 modules. Among them, there are 4 important components like Login page, Adding student details, Updating it and Deleting it. As a part of smoke testing we will test the login page with valid input. After login we will test the addition, updating and deletion of records. If all the 4 critical components work fine then the build is stable enough to proceed with detailed testing. This is known as Smoke testing.

When to use smoke testing

Smoke testing is used in the following scenarios:

  • It is done by developers before giving build to the testing team.
  • It is done by the testers before they start the detailed testing.
  • Smoke testing is done to ensure that the basic functionalities of the application are working fine.

Advantages of Smoke testing

  • It helps in finding the bugs in the early stage of testing.
  • It helps in finding the issues that got introduced by the integration of components.
  • It helps in verifying the issues fixed in the previous build are NOT impacting the major functionalities of the application.
  • Very limited number of test cases is required to do the smoke testing.
  • Smoke testing can be carried out in small time.

Disadvantages of Smoke testing

  • Smoke testing does not cover the detailed testing.
  • It’s a non-exhaustive testing with small number of test cases because of which we not are able to find the other critical issues.

Smoke testing is not performed with negative scenarios and with invalid data.

Difference between regression testing and retesting

Before we start with the differences between regression testing and retesting it’s good to have simple understanding of each topic. Basically, regression testing is carried out to ensure that the existing functionality is working fine and there are no side effects of any new change or enhancements done in the application. In other words, Regression Testing checks to see if new defects were introduced in previously existing functionality. [Read more…]

What is Retesting? When to use it? Advantages and Disadvantages

Retesting is testing of a particular bug after it has been fixed. Usually tester raises the bug when they find it while testing the product or its component. This bug is assigned to a developer and he fixes it. Post fixing the bug is assigned to the tester for its verification. This testing is known as retesting. [Read more…]

200+ Software Testing Interview Questions and Answers PDF

People often ask us for software testing interview questions and answers. At the end of this post you will find the link to download the PDF with 202 Software Testing Interview Question and Answers.

Before we get to that, it’s useful to understand the types of questions that are asked during interviews. The questions can be majorly categorized under three categories. [Read more…]

21 Qualities Of A Good Software Tester

Every organization is using technology these days. From big media to textile giants, mutual funds to startups, each one has their unique requirements for software and automation. While development and implementation of the software is vital to these organizations, there is a growing need for good software testers who love testing. There is no shortage of software tester jobs that pay a good salary. One commonly asked question is “How to become a software tester?” Before one goes into the technical details of software testing, its important to ensure that you have the characteristics required for a tester. [Read more…]

What is the difference between ISTQB Certification and ISEB/BCS Certification and CTFL Certification?

One commonly asked question is what is the difference between ISTQB certification and ISEB certification? What is BCS? What is CTFL. With so many acronyms and terms associated with the ISTQB certification exam it is easy for new candidates to get confused between them. The below points will clearly answer any questions you may have and eliminate the confusion surrounding these topics.

If you find this useful, please share this page with your friends.

[Read more…]

How to pass ISTQB Foundation exam certification in your first attempt

Here are few Tips and Tricks to pass the ISTQB Foundation Level Certification Exam in first attempt. ISTQB Exam is one of the most widely recognized exams for Software Testing professionals. Many organization are making it mandatory for their employees to take up this exam. The exam is not very tough but sometimes people underestimate the difficulty level of the exam, do not study enough and fail the exam.

The below tips are aimed at helping you prepare well for the exam so that you can pass it in your first attempt.

If you find this useful, please share this page with your friends. [Read more…]

Best Test Management Tools – Web based

Test management tools take care of the entire end to end QA processes. It is used to keep track of the information like Test strategy, Test planning, Test cases and it also keeps the track of all the bugs raised and much more. There are many different types of test management tools which come with different features which are suitable for different types of testing. Most test management tools allow you to start working with them without having to install anything on your machine. This allows the tester to collaborate with his/her team from any where. Below we list some of the best web based test management tools. [Read more…]