International Software Testing Qualification Board

Welcome to: ISTQB Foundation Level exam preparation Course https://arshadqa.com/

Course Objectives https://arshadqa.com/

Question Distribution Chapter Wise https://arshadqa.com/

What is Quality?

Antonym of Quality Inferiority

Software Quality: Definition 1 Low levels of defects when deployed, ideally approaching zero

Software Quality: Definition 2 A majority of clients with high user-satisfaction when surveyed

Software Quality: Definition 3 A structure that can minimize ―bad fixes‖ or insertion of new defects during repairs

Software Quality: Definition 4 Effective customer support when problems do occur

Software Quality: Definition 5 Rapid repairs for defects, especially for high-severity defects

Beyond Absence of Defects

Why Software Quality? https://arshadqa.com/

Software Quality Assurance ? So the term software quality assurance would mean that the software guarantees high quality

ISTQB Foundation Level exam preparation https://arshadqa.com/

https://arshadqa.com/

ISTQB Foundation New Syllabus https://arshadqa.com/

Introduction To ISTQB

ISTQB Foundation Syllabus

ISTQB Foundation Level exam preparation https://arshadqa.com/

1.1 What is testing?

Fundamentals of testing

What is testing? (K2) https://arshadqa.com/

Test Process https://arshadqa.com/

Objectives of Testing https://arshadqa.com/

What is testing? (Classification of Testing) https://arshadqa.com/

What is testing? (Classification of Testing)

What is testing? (Debugging and Testing) Testing Testing deal with finding the defects by conducting failure on application or product. This activity is performed by testers. Debugging Debugging is a development activity which deals with analyzing these defects, finding the root cause and removes the cause of defects. This activity is commonly performed by developers.

ISTQB Foundation Level exam preparation

1.2 Why testing is necessary?

1.2 Why is Testing Necessary?

Why is Testing Necessary?

Quality Assurance & Quality Control

Error, Defect & Failure Error(Mistake) A human action that produces an incorrect result Fault(Defect, Bug) A manifestation of an error in software Also know as a defect or bug If executed, a fault may cause a failure Failure: Deviation of the software from its expected delivery or service

Causes of Software Defects

ISTQB Foundation Level exam preparation

Fundamentals of Testing

1.3 Principles of Testing

Principle 1: Testign Shows presence of Defects

Principle 2: Exhaustive testing is impossible

Principle 3: Early testing: It saves time and money

Principle 4 : Defect Clustering https://arshadqa.com/

Principle 5 : pesticide paradox https://arshadqa.com/

Principle 6: Testing is Context dependent

Principle 7: Absence-of-error fallacy Meeting the requirement is equally important. Finding and fixing defect doesn’t help if the system built doesn’t fulfill the users’ need and expectations.

Testing Principles These principles provide a foundation for making informed decisions during the testing process. By applying these principles, testers can focus on high-risk areas, avoid common pitfalls, and ensure that their testing is both efficient and effective.

ISTQB Foundation Level exam preparation

1.4 Test Process – part 1 https://arshadqa.com/

1.4 Test Process – part 1

1.4 Test Process In a QA (Quality Assurance) role, it’s crucial to remember the key aspects of the test process to ensure thorough and effective testing.

Test Process:

Test Planning

Test monitoring and control

Test Process

Test Analysis

Test Design

Test Process

Test implementation

Test Execution

Test Completion

ISTQB Foundation Level exam preparation

1.4 Test Process – part 2 https://arshadqa.com/

Test work products

Test Work Products:

Traceability between the test basis and test work products

ISTQB Foundation Level exam preparation https://arshadqa.com/

1.5 Psychology of testing https://arshadqa.com/

Human psychology and testing

Ways to communicate well

1.5.2 Tester’s and Developer’s Mindsets

A developer’s mindset

Independent Testing

Levels of Independent Testers

ISTQB Foundation Level exam preparation https://arshadqa.com/

Chapter: 02 Testing throughout the software life cycle https://arshadqa.com/

2. Testing throughout the software life cycle

Testing throughout the software life cycle

2.1 Software development models V-Model (Sequential Development Model)

Testing within a life cycle model

Software Development Model

Iterative Development Model Examples

Software Development Lifecycle Models in Context

ISTQB Foundation Level exam preparation

2.2 Test Levels

2.2.1 Component Testing

2.2.1 Component Testing Test basis Examples of work products that can be used as a test basis for component testing include: Detailed design Code Data model Test objects Typical test objects for component testing include: Components, units or modules Code and data structures Classes Database modules https://arshadqa.com/

2.2.2 Integration Testing Integration testing focuses on interactions between components or systems. Objectives of integration testing include: Reducing risk Verifying whether the functional and non-functional behaviors of the interfaces are as designed and specified Building confidence in the quality of the interfaces Finding defects (which may be in the interfaces themselves or within the components or systems) Preventing defects from escaping to higher test levels https://arshadqa.com/

Test basis

Test objects

2.2.3 System Testing https://arshadqa.com/

Test basis

Test objects

2.2.4 Acceptance Testing

Specific approaches and responsibilities

Test basis

Test objects

ISTQB Foundation Level exam preparation https://arshadqa.com/

2.3 Test Types

Test Types Objectives

2.3.1 Functional Testing

2.3.2 Non-functional Testing Non-functional testing of a system evaluates characteristics of systems and software such as usability, performance efficiency or security Non-functional testing can and often should be performed at all test levels, and done as early as possible Non-functional test design and execution may involve special skills or knowledge, such as knowledge of the inherent weaknesses of a design or technology

2.3.3 White-box Testing White-box testing derives tests based on the system’s internal structure or implementation White-box test design and execution may involve special skills or knowledge, such as the way the code is built

2.3.4 Change-related Testing

2.3.5 Test Types and Test Levels It is possible to perform any of the test types mentioned above at any test level Functional, non-functional, white-box, and change-related tests will be given across all test levels which is Component testing Integration testing System testing Acceptance testing

ISTQB Foundation Level exam preparation https://arshadqa.com/

2.4 Maintenance Testing https://arshadqa.com/

2.4 Maintenance Testing

The scope of maintenance testing

2.4.1 Triggers for Maintenance

2.4.1 Triggers for Maintenance For Internet of Things systems, maintenance testing may be triggered by the introduction of completely new or modified things, such as hardware devices and software services, into the overall system. The maintenance testing for such systems places particular emphasis on integration testing at different levels (e.g., network level, application level) and on security aspects, in particular those relating to personal data.

2.4.2 Impact Analysis for Maintenance

ISTQB Foundation Level exam preparation https://arshadqa.com/

3 Static Testing

3.1 Static Testing Basics

3.1.1 Work Products that Can Be Examined by Static Testing

3.1.2 Benefits of Static Testing

3.1.3 Differences between Static and Dynamic Testing

Typical defects

ISTQB Foundation Level exam preparation https://arshadqa.com/

3.2 Review Process https://arshadqa.com/

3.2 Review Process

3.2.1 Work Product Review Process

Review Planning

Initiate review

Individual review

Issue communication and analysis

Fixing and reporting Creating defect reports for those findings that require changes Fixing defects found (typically done by the author) in the work product reviewed Communicating defects to the appropriate person or team (when found in a work product related to the work product reviewed) Recording updated status of defects (in formal reviews), potentially including the agreement of the comment originator Gathering metrics (for more formal review types) Checking that exit criteria are met (for more formal review types) Accepting the work product when the exit criteria are reached

3.2.2 Roles and responsibilities in a formal review

Author Creates the work product under review Fixes defects in the work product under review (if necessary)

Management

Moderator Ensures effective running of review meetings (when held) Mediates, if necessary, between the various points of view Is often the person upon whom the success of the review depends

Review leader Takes overall responsibility for the review Decides who will be involved and organizes when and where it will take place

Reviewers

Scribe (or recorder) Collates potential defects found during the individual review activity Records new potential defects, open points, and decisions from the review meeting (when held)

3.2.3 Review Types One of the main objective of review is to uncover defects

Informal review

Walkthrough

Technical review

Inspection

3.2.4 Applying Review Techniques

3.2.5 Success Factors for Reviews

People-related success factors for reviews

ISTQB Foundation Level exam preparation https://arshadqa.com/

4 Test Techniques https://arshadqa.com/

4.1 Categories of Test Techniques

Black Box Test Techniques

White Box https://arshadqa.com/

Experience base

4.1.1 Choosing Test Techniques

ISTQB Foundation Level exam preparation https://arshadqa.com/

4.2 Black-box Test Techniques

4.2 Black-box Test Techniques https://arshadqa.com/

4.2 Black-box Test Techniques

4.3 White-box Test Techniques

4.2.1 Equivalence Partitioning Equivalence partitioning or equivalence class partitioning (ECP) is a software testing technique that divides the input data of a software unit into partitions of equivalent data from which test cases can be derived. In principle, test cases are designed to cover each partition at least once.

4.2.1 Equivalence Partitioning

ISTQB Foundation Level exam preparation

https://arshadqa.com/

4.2.2 Boundary Value Analysis

4.2.2 Boundary Value Analysis A text field in a application accepts inputs as the age of user. Here, the values allowed to be accepted by the field is between 18 to 30 years, inclusive of both the values. By applying BVA what is the minimum number of test cases require for maximum coverage 2 3 1 4

4.2.2 Boundary Value Analysis A text field in a application accepts inputs as the age of user. Here, the values allowed to be accepted by the field is between 18 to 30 years, inclusive of both the values. Based on Boundary value analysis which is the given option consist of valid collection of boundary values. 16, 17, 19, 30 17, 18, 19, 31 17, 18, 30, 31 18, 19, 20, 31 https://arshadqa.com/

4.2.2 Boundary Value Analysis A text field in a application accepts inputs as the age of user. Here, the values allowed to be accepted by the field is between 18 to 30 years, inclusive of both the values. By applying EP and BVA which of the given option consist of valid boundary values and valid equivalence values. 17, 18, 20 18, 30, 25 18, 30, 31 19, 20, 31 https://arshadqa.com/

ISTQB Foundation Level exam preparation

4.2.3 Decision Table Testing

4.2.3 Decision Table Testing https://arshadqa.com/

4.2.3 Decision Table Testing What is the expected result for each of the following test cases? A. Citibank card member, holding a sliver room B. Non Citibank member, holding a platinum room https://arshadqa.com/

4.2.3 Decision Table Testing A- Don’t offer any upgrade, B- Don’t offer any upgrade. A-Don’t offer any upgrade, B- Offer upgrade to Gold A-Offer upgrade to silver, B-Offer upgrade to silver A-Offer upgrade to Gold, B-Don’t offer any upgrade.

4.2.3 Decision Table Testing Given the following decision table: Which of the following test cases and expected results is VALID? 23 year old in insurance class A Premium is 90 and access is 2,500. 51 year old in insurance class C Premium is 100 and access is 500. 31 year old in insurance class B Premium is 70 and access is 2,500. 43 year old in insurance class C Premium is 100 and access is 1,000.

ISTQB Foundation Level exam preparation

4.2.4 State Transition Testing https://arshadqa.com/

4.2.4 State Transition Testing

guard condition If the same event can result in two or more different transitions from the same state, that event may be qualified by a guard condition.

4.2.4 State Transition Testing State transition diagram for water

4.2.4 State Transition Testing Based on the given state transition diagram of a switch which of the following test case in INVALID? Off to On On to Off FAULT to On On to FAULT

ISTQB Foundation Level exam preparation https://arshadqa.com/

4.2.5 Use Case Testing https://arshadqa.com/

4.2.5 Use Case Testing

4.2.5 Use Case Testing Which of the following statements about the benefits of deriving test cases from use cases are true and which are false? A. Driving test cases from use cases is helpful for system and acceptance testing B. Driving test cases from use cases is helpful only for automated testing. C. Driving test cases from use cases is helpful for component testing. D. Driving test cases from use cases is helpful for integration testing. Answer set: A. A and D are true; B and C are false B. A is true; B, C, an D are false. C. B and D are true; A and C are false D. A, C and D are true; B is false https://arshadqa.com/

ISTQB Foundation Level exam preparation https://arshadqa.com/

4.3 White-box Test Techniques 4.3.1 Statement Testing and Coverage https://arshadqa.com/

4.3 White-box Test Techniques

4.3.1 Statement Testing and Coverage

4.3.1 Statement Testing and Coverage Read A Read B If A>B then Print “ A is Bigger” ELSE Print “ B is Bigger” End If Statement coverage: 2 Tip : number of else +1 https://arshadqa.com/

4.3.1 Statement Testing and Coverage Read A Read B If A>B then Print “ A is Bigger” ELSE Print “ B is Bigger” End If What is the minimum number of test cases require for 100% test coverage?

4.3.1 Statement Testing and Coverage Read A If A>0 then If A=21then Print “Key” End If End If Statement coverage: 1 Tip for unnested condition: number of else

4.3.1 Statement Testing and Coverage Read A Read B If A>0 then If B=0 then Print “No values” Else Print B If A>21 then Print A End If End If End If Nested condition: Statement coverage= 2 Tip: number of else +1

4.3.1 Statement Testing and Coverage Read A Read B If A<0 then Print “ A negative” Else Print “A Positive” End if If B<0 then Print “B negative” Else Print “B Positive” End If Tip: Unnested condition: number of else Statement coverage = 2

4.3.1 Statement Testing and Coverage Tip for un-nested conditions Statement coverage = number of else Tip for nested conditions: Statement coverage = number of else +1

4.3.1 Statement Testing and Coverage For the given fragment of code following paths/test cases have been executed . What statement coverage is achieved? Test 1-A,B,C Test 2-A,B,D,G,H A. 50% B. 75% C. 90% D. 100%

4.3.1 Statement Testing and Coverage Statement Coverage = Number of statement executed /Total number of statements =(6/8)*100=75%

ISTQB Foundation Level exam preparation

4.3 White-box Test Techniques 4.3.2 Decision Testing and Coverage https://arshadqa.com/

4.3.2 Decision Testing and Coverage

4.3.2 Decision Testing and Coverage Read A Read B If A>B then Print “ A is Bigger” ELSE Print “ B is Bigger” End If Decision Coverage = 2

4.3.2 Decision Testing and Coverage Read A Read B If A>B then Print “ A is Bigger” ELSE Print “ B is Bigger” End If What is the minimum number of test cases require for 100% decision coverage?

4.3.2 Decision Testing and Coverage Read A If A>0 then If A=21then Print “Key” End If End If Decision Coverage = 3 Tip for nested conditions Decision coverage = number of ifs +1

4.3.2 Decision Testing and Coverage Read A Read B If A>0 then If B=0 then Print “No values” Else Print B If A>21 then Print A End If End If End If Decision Coverage = 4 Tip for nested conditions Decision coverage = number of ifs +1

4.3.2 Decision Testing and Coverage Read A Read B If A<0 then Print “ A negative” Else Print “A Positive” End if If B<0 then Print “B negative” Else Print “B Positive” End If Decision coverage = 2 Tip for un-nested conditions Decision coverage = 2 (regardless of number of ifs )

4.3.2 Decision Testing and Coverage Tip for un-nested conditions Decision coverage = 2 (regardless of number of ifs ) Tip for nested conditions Decision coverage = number of ifs +1 https://arshadqa.com/

4.3.2 Decision Testing and Coverage For the given fragment of code following paths/test cases have been executed . What decision coverage is achieved? Test 1-A,B,C Test 2-A,B,D,G,H A. 62% B. 75% C. 90% D. 100% https://arshadqa.com/

4.3.2 Decision Testing and Coverage Decision Coverage = Number of branch executed /Total number of branches =(5/8)*100=62% https://arshadqa.com/

ISTQB Foundation Level exam preparation https://arshadqa.com/

4.4 Experience-based Test Techniques https://arshadqa.com/

4.4 Experience-based Test Techniques

4.4 Experience-based Test Techniques 4.4.1 Error Guessing 4.4.2 Exploratory Testing 4.4.3 Checklist-based Testing https://arshadqa.com/

4.4.1 Error Guessing

4.4.2 Exploratory Testing https://arshadqa.com/

4.4.3 Checklist-based Testing

ISTQB Foundation Level exam preparation https://arshadqa.com/

5 Test Management https://arshadqa.com/

5 Test Management Test Management refers to the process of organizing and controlling the testing activities during the software development lifecycle. It involves planning, execution, monitoring, and reporting to ensure that the software product meets the desired quality standards. Effective test management ensures that all testing activities are streamlined, documented, and controlled to minimize risk and defects.

5.1 Test Organization

5.1.1 Independent Testing

Potential benefits of test independence

Potential drawbacks of test independence

5.1.2 Tasks of a Test Manager and Tester In this syllabus, two test roles are covered, test managers and testers. The activities and tasks performed by these two roles depend on the project and product context, the skills of the people in the roles, and the organization.

Test Manager Tasks t

Test Manager Tasks

tester tasks

ISTQB Foundation Level exam preparation

5.2 Test Planning and Estimation https://arshadqa.com/

Test Plan

Test Strategy A test strategy provides a generalized description of the test process. Analytical: Model-Based Methodical Process-compliant Directed Regression-averse Reactive https://arshadqa.com/

Entry Criteria

Exit criteria

Test Execution Schedule https://arshadqa.com/

Factors Influencing the Test Effort Factors influencing the test effort may include characteristics of the product, characteristics of the development process, characteristics of the people, and the test results.

Product characteristics

Development process characteristics

People characteristics

Test results

Test Estimation Techniques https://arshadqa.com/

ISTQB Foundation Level exam preparation https://arshadqa.com/

5.3 Test Monitoring and Control https://arshadqa.com/

5.3 Test Monitoring and Control

5.3.1 Metrics Used in Testing

Common test metrics include

5.3.2 Purposes, Contents, and Audiences for Test Reports

Typical test progress reports and test summary reports may include

ISTQB Foundation Level exam preparation https://arshadqa.com/

5.4 Configuration Management https://arshadqa.com/

5.4 Configuration Management

configuration management may involve ensuring the following

ISTQB Foundation Level exam preparation

5.5 Risks and Testing https://arshadqa.com/

5.5 Risks and Testing

5.5.2 Product and Project Risks

Product Risks

Project risk

5.5.3 Risk-based Testing and Product Quality

ISTQB Foundation Level exam preparation

5.6 Defect Management https://arshadqa.com/

5.6 Defect Management

ISTQB Foundation Level exam preparation https://arshadqa.com/

Chapter 6 6 Tool Support for Testing

6.1 Test Tool Considerations https://arshadqa.com/

6.1 Test Tool Considerations

6.1.1 Test Tool Classification

Tool support for management

Tool support for static testing

Tool support for test design and implementation

Tool support for test execution and logging

Tool support for performance measurement and dynamic analysis

Tool support for specialized testing needs

6.1.2 Benefits and Risks of Test Automation

Potential benefits of using tools to support test execution include

Potential risks of using tools to support testing include

Potential risks of using tools to support testing include The effort required to maintain the test assets generated by the tool may be under-estimated The tool may be relied on too much Version control of test assets may be neglected

Potential risks of using tools to support testing include

ISTQB Foundation Level exam preparation

6.2 Effective Use of Tools https://arshadqa.com/

6.2.1 Main Principles for Tool Selection

6.2.2 Pilot Projects

6.2.3 Success Factors for Tools

Question Distribution Chapter Wise https://arshadqa.com/

Thanks https://arshadqa.com/

International Software Testing Qualification Board

About This Presentation

Slide Content

Tags

Categories

Download

Quick Actions

Statistics

Related Slideshows

International Software Testing Qualification Board

About This Presentation

Slide Content

Slide 1

Slide 2

Slide 3

Slide 4

Slide 5

Slide 6

Slide 7

Slide 8

Slide 9

Slide 10

Slide 11

Slide 12

Slide 13

Slide 14

Slide 15

Slide 16

Slide 17

Slide 18

Slide 19

Slide 20

Slide 21

Slide 22

Slide 23

Slide 24

Slide 25

Slide 26

Slide 27

Slide 28

Slide 29

Slide 30

Slide 31

Slide 32

Slide 33

Slide 34

Slide 35

Slide 36

Slide 37

Slide 38

Slide 39

Slide 40

Slide 41

Slide 42

Slide 43

Slide 44

Slide 45

Slide 46

Slide 47

Slide 48

Slide 49

Slide 50

Slide 51

Slide 52

Slide 53

Slide 54

Slide 55

Slide 56

Slide 57

Slide 58

Slide 59

Slide 60

Slide 61

Slide 62

Slide 63

Slide 64

Slide 65

Slide 66

Slide 67

Slide 68

Slide 69

Slide 70

Slide 71

Slide 72

Slide 73

Slide 74

Slide 75

Slide 76

Slide 77