ISTQB FOUNDATION 4.0 | Tutorial 60 | Exam Details & Tips | ISTQB Foundation Level Summary in 30 Mins

Summary

This ISTQB Foundation Level 4.0 tutorial series concludes with a comprehensive summary, guiding viewers through the key concepts covered in each chapter. The video emphasizes the importance of understanding fundamental software testing principles, testing throughout the development lifecycle, static and dynamic testing techniques, and the role of test management and tools. It also provides strategic advice for exam preparation, highlighting the significance of chapters 1, 4, and 5, and clarifies the exam's question format, including multi-select questions.

Takeaways

• 📚 The video provides a comprehensive summary of the ISTQB Foundation Level 4.0 syllabus, covering all chapters and key aspects for examination preparation.
• 🔍 It emphasizes the importance of understanding the fundamental concepts of software testing, including testing principles, test activities, and roles within the testing lifecycle.
• 📈 The tutorial highlights the significance of early and frequent feedback in the agile methodology to ensure alignment with business requirements and timely correction of deviations.
• 📝 The script discusses various testing techniques under black box, white box, and experience-based categories, stressing the importance of selecting the right technique based on the testing context.
• 🛠️ Chapter 3 focuses on static testing, explaining the difference between reviews and static analysis, and the importance of early defect detection to improve productivity.
• 🔑 The video script explains the seven standard principles of testing, which are crucial for understanding the rationale behind testing practices.
• 📉 The importance of risk management in testing is underscored, detailing the processes of risk identification, assessment, mitigation, and control.
• 👥 The roles of a test manager and test engineer are differentiated, with the former focusing on planning and monitoring, and the latter on analysis, design, and execution.
• 🔢 The script provides an overview of test management activities, including test planning, estimation, scheduling, and the use of matrices for monitoring and control.
• 🛡️ Configuration management is highlighted as a critical process for version control, traceability, and managing revisions, typically supported by tools.
• 🔧 The benefits and risks of using test tools are briefly discussed, encouraging a balanced approach to tool utilization in the testing process.

Q & A

What are the key topics covered in the first chapter of the ISTQB Foundation Level 4.0 syllabus?

The first chapter covers fundamental software testing concepts, including testing and debugging, QA and QC, basic terminologies like error, mistake, bug, fault, defect, and failure, as well as the relationship between fault and failure, root cause analysis, and the impact of fixes on a system.

Why is testing considered important in the software development life cycle?

Testing is important because it helps identify defects early in the development process, which saves time and money. Testers contribute to the overall lifecycle by being proactively involved, conducting static and dynamic testing, and ensuring quality assurance.

What are the seven standard principles of testing mentioned in the script?

The seven principles are: 1) Testing shows the presence of defects, not their absence. 2) Exhaustive testing is impossible. 3) Early testing saves time and money. 4) Defects cluster, meaning they are not evenly distributed. 5) Tests wear out, indicating the need for test suite revision over time. 6) Testing is context-dependent. 7) The absence of defects can also be a failure, emphasizing the importance of requirements.

What are the different phases of test activities mentioned in the script?

The phases of test activities include planning, monitoring and control, test analysis, test design, test implementation, test execution, and test completion.

What is the difference between static testing and dynamic testing?

Static testing involves the examination of documents or code without executing the program, while dynamic testing involves running the program with various inputs to check for errors and defects.

What are the roles of a test manager and a test engineer as per the ISTQB Foundation Level 4.0 syllabus?

A test manager is responsible for planning, monitoring, controlling, and completing the test activities. A test engineer is responsible for analysis, design, execution, and implementation of tests.

What is the significance of test levels and test types in the software development life cycle?

Test levels and types define the various stages and approaches to testing within the software development life cycle. They help in identifying the scope and focus of testing at each level, such as unit testing, integration testing, system testing, and acceptance testing.

What is the difference between functional and non-functional testing?

Functional testing focuses on testing the functionality of the software against the requirements, whereas non-functional testing evaluates the performance, security, usability, and other quality attributes of the software.

What is the importance of traceability in testing?

Traceability is crucial as it ensures that all testing activities and results are linked back to the original requirements, providing coverage and facilitating the tracking of changes and issues throughout the testing process.

What are the key aspects of test management covered in the ISTQB Foundation Level 4.0 syllabus?

Key aspects of test management include test planning, estimation, the use of test matrices, entry and exit criteria, risk management, configuration management, and defect management.

What is the role of a checklist in experience-based test techniques?

A checklist in experience-based test techniques provides a set of questions or criteria that testers should consider while interacting with or testing the product. It helps ensure that common issues are not overlooked and that testing is thorough.

What are the benefits and risks of using test tools as mentioned in the script?

Benefits of using test tools include increased efficiency, automation of repetitive tasks, and improved test coverage. Risks involve potential over-reliance on tools, which may lead to missed defects that require human judgment, and the possibility of tool limitations not being fully understood or addressed.

How is the question paper for the ISTQB Foundation Level 4.0 certification exam structured?

The exam consists of 40 questions with a specific distribution: Chapter 1 has 8 questions, Chapter 2 has 6, Chapter 3 has 4, Chapter 4 has 11, Chapter 5 has 9, and Chapter 6 has 2. Some questions may have five options, requiring the selection of two correct answers.

Outlines

00:00

📚 ISTQB Foundation Level 4.0 Tutorial Overview

This paragraph introduces the final summary video of the ISTQB Foundation Level 4.0 tutorial series. It mentions the completion of all chapters and the intention to guide viewers through a quick summarization of the entire syllabus in a single video. The speaker also highlights the importance of understanding key aspects and preparation tips for the examination. The video promises to sequentially revisit each chapter, starting with the fundamentals of software testing, and emphasizes the significance of grasping basic terminologies, concepts, and principles for effective test preparation.

05:01

🔍 In-Depth Chapter 1: Fundamentals of Software Testing

Chapter 1 is dissected in this paragraph, focusing on the fundamentals of software testing. It covers five major topics including basic concepts, the importance of testing, principles of testing, test activities and roles, and various test artifacts. The paragraph delves into the significance of understanding the relationship between faults and failures, the role of testers in the lifecycle, and the seven standard testing principles. It also touches on the importance of test planning, monitoring, and the different phases of testing activities. The paragraph concludes with a reminder of the importance of understanding these elements to avoid being misled by tricky examination questions.

10:03

🔧 Chapter 2: SDLC and Testing Practices

The second paragraph discusses Chapter 2, which is about software development life cycles (SDLC) and how testing is integrated within them. It explains how testing efforts and contributions vary across different SDLC models and emphasizes four golden characteristics that are applicable to any development model. The paragraph also covers the unique testing practices in various life cycles, the concept of shift-left testing in DevOps, and the importance of retrospectives for process improvement. Additionally, it outlines the different test levels and types, including unit, integration, system, acceptance, and maintenance testing, as well as the distinction between functional and non-functional testing.

15:03

📝 Chapter 3: Static Testing Techniques and Principles

This paragraph focuses on Chapter 3, which deals with static testing. It explains the importance of static testing in identifying defects before dynamic testing and enhancing productivity. The paragraph distinguishes between two methods of static testing: reviews and static analysis. It also discusses the types of documents suitable for review, the differences between static and dynamic testing, and the significance of early and frequent feedback. The formal review process, including its stages and roles, is detailed, along with the types of reviews and their unique characteristics. The paragraph concludes with an emphasis on the importance of understanding static testing for effective quality assurance.

20:04

🛠️ Chapter 4: Test Analysis and Design Approaches

The fourth paragraph explores Chapter 4, which is centered on test analysis and design techniques. It categorizes these techniques into black-box, white-box, and experience-based testing. For each category, the paragraph outlines specific techniques such as equivalence partitioning, boundary value analysis, decision table testing, state transition testing, statement testing, branch testing, error guessing, exploratory testing, and checklist-based testing. The importance of understanding the basis for each technique and the unique aspects of each is highlighted. The paragraph also touches on test analysis approaches, acceptance criteria, and acceptance test-driven development, emphasizing the practical application of these concepts in testing.

25:05

📊 Chapter 5: Test Management and Key Processes

Chapter 5 is highlighted in this paragraph, focusing on test management and its associated processes. It covers test planning, estimation, matrices, entry and exit criteria, and other fundamental test activities. The paragraph delves into risk management, detailing the steps of identification, assessment, mitigation, and control. It also introduces configuration management, emphasizing version control, unique identification, traceability, and revision history. Defect management is also discussed, including the purpose of a defect report and its components. The paragraph underscores the importance of these management practices for the overall success of testing endeavors.

🛠️ Chapter 6: Test Tools and Their Significance

The final paragraph of the script addresses Chapter 6, which provides an introduction to test tools. It outlines the types of test tools available and discusses the benefits and risks associated with their use. The paragraph emphasizes that while the chapter is brief, it is crucial for understanding how tools can aid in testing processes and that it should not be overlooked in preparation for the examination. The paragraph concludes with a reminder of the importance of all chapters and an encouragement to continue learning and exploring the subject matter.

🎯 Final Summary and Examination Tips

This concluding paragraph wraps up the tutorial by summarizing the entire syllabus and providing examination tips. It emphasizes the importance of not neglecting any chapter, especially highlighting Chapters 1, 4, and 5 as critical for success. The paragraph also provides a breakdown of the examination structure, with 40 questions distributed among the chapters, and notes that some questions will have five options with a requirement to select two correct answers. It advises learners to be thorough in their preparation and offers assistance for any queries, concluding with well-wishes for their learning journey and examination.

Keywords

💡ISTQB Foundation Level 4.0

ISTQB Foundation Level 4.0 refers to the latest version of the standard syllabus for the International Software Testing Qualifications Board (ISTQB) certification at the foundation level. It is the core subject of the video, which aims to summarize the entire syllabus and prepare viewers for the certification exam. The script covers the chapters and key concepts that are part of this syllabus.

💡Testing

Testing is the process of evaluating a system or component to detect any defects or errors. It is a fundamental concept in the video, which discusses various aspects of testing such as its importance, principles, and types. For instance, the script mentions 'fundamentals of software testing' and 'concepts of testing' as part of the first chapter.

💡Quality Assurance (QA) and Quality Control (QC)

Quality Assurance (QA) and Quality Control (QC) are two key components of the software development process. QA is a set of processes that ensure quality is built into the product, while QC is the process of checking that the product meets the required quality standards. The script introduces these terms in the context of fundamental software testing concepts.

💡Static Testing

Static Testing is the process of evaluating a system or its documentation without executing the system. It is one of the main topics in the video, where the script discusses its importance, principles, and various techniques such as reviews and static analysis, which are used to identify defects in the early stages of the software development life cycle.

💡Dynamic Testing

Dynamic Testing involves executing the system and examining its behavior to identify defects. The video script contrasts static and dynamic testing, emphasizing that not all defects can be found through static testing alone, hence the necessity of dynamic testing methods.

💡Test Design

Test Design is the process of creating test cases and determining the test environment setup. It is a critical activity within the testing process, as mentioned in the script, where it discusses the relationship between test design and test implementation, such as identifying test data and designing the test environment.

💡Defect Clustering

Defect Clustering is a principle that states defects are not uniformly distributed throughout a system but tend to cluster in certain areas. The script explains this concept as part of the seven standard principles of testing, indicating that focusing testing efforts on these areas can be more effective.

💡Test Levels

Test Levels refer to the different stages of testing that occur throughout the software development life cycle, such as unit testing, integration testing, system testing, and acceptance testing. The script discusses these levels to explain how testing is conducted at various stages to ensure software quality.

💡Risk Management

Risk Management is the process of identifying, assessing, and controlling risks that could impact the project or product. The video script covers this concept as part of the test management chapter, explaining the steps involved in risk identification, assessment, mitigation, and control.

💡Configuration Management

Configuration Management is the discipline of tracking and controlling changes to a project's deliverables. The script highlights the importance of version control, unique identification, traceability, and managing the history of revisions within this process, which is crucial for maintaining consistency and understanding changes over time.

💡Test Tools

Test Tools are software applications that support the testing process by providing capabilities for test design, execution, and reporting. The script briefly introduces the types of test tools available, their benefits, and the risks associated with their use, emphasizing the value they add to the testing process.

Highlights

Introduction to ISTQB Foundation Level 4.0 certification and its significance in software testing.

Completion of all chapters with a focus on summarization and key aspects for examination preparation.

Explanation of fundamental software testing concepts including QA, QC, and basic terminologies.

Importance of understanding the relationship between error, fault, defect, and failure in testing.

Discussion on the psychological aspect of testing and the tester's contribution to the software development lifecycle.

Seven standard principles of testing with emphasis on their application and impact on testing practices.

Overview of test activities and roles, including planning, monitoring, and control within the testing process.

Differentiation between various test levels such as unit, integration, system, and acceptance testing.

Understanding of functional and non-functional testing and their distinct levels.

Introduction to static testing, its importance, and its role in process improvement and quality enhancement.

Differences between static and dynamic testing, and the types of defects each can reveal.

The formal review process in software testing, including its stages and roles involved.

Importance of early and frequent feedback in aligning with business requirements and avoiding deviations.

Test analysis and design approaches, including black box, white box, and experience-based techniques.

Explanation of test management activities such as planning, estimation, and risk management.

Configuration management's role in version control, traceability, and managing revisions history.

Defect management process, including reporting, tracking, and the importance of a well-structured defect report.

Overview of test tools, their types, benefits, and associated risks in a testing environment.

Question breakdown for the ISTQB examination, emphasizing the weightage of each chapter.

Emphasis on the importance of understanding rather than memorizing for effective examination preparation.

Closing remarks encouraging continuous learning, exploration, and understanding in software testing.

Transcripts

Hello friends and greetings for the day

welcome back to another episode of our

tutorials on istqb Foundation level 4.0

finally we have completed all the

chapters and it's time for us to do a

quick summarization so this video will

be completely guiding you with what we

have covered so far in one single video

and at the same time we'll also be

talking about the key important aspects

of this entire training at the same time

what are the things what you need to

take care of when you do your

preparation before the examination

ations so to get started we'll be

looking into each chapter one by one and

then getting into the conclusion of

[Music]

it well to start with the very first

chapter which is called as fundamental

soft testing of course here we covered

five major topics the very first topic

for you had was related to the concepts

uh of fundamental soft testing which

included keywords like testing and

debugging talking about QA and QC which

is quality assurance and quality control

in fact many other basic terminologies

like error mistake bug fault defect

failure the relationship between fault

and uh failure and root cause analysis

which is really to talk about how does

uh a fix off a effect turns into uh root

cause analysis and how root cause fixing

would impact or create a side effect

introducing regressions into a system so

it's very crucial for someone to

understand these relationships and uh

deal with them at the same time so what

is testing which is fundamentals of

concepts of testing was covered in the

very first topic then we went through

why testing is important of course in

part of why testing is important we went

through the psychological aspect of

testing that why it is important for

someone else to test and how exactly

testers contribute to the overall life

cycle by being proactively participating

throughout the life cycle uh by

conducting initially static testing and

later down the line the dynamic testing

so testing has a complete different set

of contribution to be made when it comes

to the overall process which we covered

as a part of test when we came to the

third segment we spoke about principles

of testing there we covered seven

standard principles of testing number

one testing shows presence of defect not

their absence number two exhaustive

testing is impossible so we have

techniques to cater them and techniques

will help you reduce the number of test

cases but do not try to test all

possible combinations of data which is

input principle number three early

testing saves time and money so static

testing is important tester should be

involved as soon as the first drafts are

available and get involved in that also

talking about the principle four which

is defect clustering defects are not

always distributed they can be gathered

together as well tests wear out which is

pesticide Paradox that any test Suite

must be revised over a period of time as

the product evolves then next one is

testing is context dependent two

different applications are not tested

with same approach and of course the

last one defect fallacy which is absence

of defect is also a failure which

certainly means that requirements are

equally important not just fixing and

finding defects so these were the seven

principles what we covered there 1.4

went through the test where the test

activities and the test roles uh test

activities are crucial here of course

every single face is important to be

remembered that what is planning what is

monitoring and control test analysis

test design test implementation test

execution and test completion and here

each phase has set of activities which

are very standardized don't forget you

need to create the relationship between

the test design and test implementation

like uh test design talks about

identifying the test data whereas test

implementation talks about preparing the

test data same way uh test design talks

about designing the environment whereas

test implementation talks about

implementing the environment so it's

it's just that key important things what

you will have to create uh an

understanding about prior to saying that

you know what exactly you have learned

so the questions will be drafted in such

way that they will try to trick you by

using these key elements from the

syllabus not just being very

straightforward so we also went through

other phases like test executions uh

there's completion and so on so we have

to know all the faces and the respective

activities uniquely as well that what's

that which does not happen in some other

faces okay so that's one thing then we

spoke about the various test Fair which

are created as a part of uh the entire

life cycle so the various work products

are like test plan test cases test

execution report defect report test

completion report and so on right so we

also learned about the traceability

there so traceability certainly builds

uh the required coverage and many other

benefits which you can always recall and

refer then we went to the testing roles

we told you that there are two standard

roles test manager and test engineer the

planning monitoring control and test

completion are the responsibilities of

the manager whereas analysis design uh

execution implementation are the

responsibilities of the test engineer

and uh the last Topic in the chapter one

we covered was related to the skill set

of a test engineer at the same time we

covered how exactly whole team approach

Works how independent a test team can be

with independence of testing and we

covered benefits and drawbacks of that

so put together these are all the key

elements which you should know at this

point of time that how exactly the

chapter one drives different context and

what are the key important things what

you should have understood right from

there moving on to the chapter 2 of

course as a part of chapter 2 we were

talking about the software development

life cycle and how testing gets

practiced here the very first segment

what you covered was related to how

testing varies in terms of efforts and

contributions when it comes to different

sdlc models it's not the same when it

comes to traditional with respect to

that of enile methodology the effort

varies and there are many other

significant characteristics which are

even applied particularly to each of

these models but at the same time you

should remember those four gold golden

characteristics which are the good

practices which can be applied to any

development model irrespective of what

you follow that is every testing

development activity must have a

corresponding testing activity each uh

uh process each level must have

objectives specific to that level at the

same time we do talk about testers

should be involved as soon as drafts are

available and uh the activities what we

get started with is test analysis and

test design right so these are the four

uh common characteristics which are

applicable to any development model and

uh irrespective of what you are

following so there are some unique

differences in terms of how testing gets

practiced in a life cycle but at the

same time we do have the common

characteristics which are applicable to

any development model and that's how

they ask you the question from so at the

same time we discuss a lot of other

things a lot of other things here

basically meant that we had an

introduction to how testing can be seen

as a driver for the development how uh

uh devops and testing work how shift

left testing is applied in the world

today then what is the need of

retrospective and how does it help in

process Improvement so there were lots

of lots of such Concepts which we

applied here and tried understanding

that testing really can be different

when it comes to different methodologies

and the way it it gets practiced needs

to be an awareness for the test engineer

to help them understand right so put

together that was the very first section

the second section covered about the

test levels of the test types as a part

of the test levels we covered about

competent testing which is also called

as unit testing

then we covered about uh component

integration testing we had system

testing then system integration testing

and then we also had something called as

acceptance testing where you covered uh

things related to Alpha and beta testing

and uh that pretty much took everything

into account right then test types of

course we differentiated between

functional and non-functional you should

know what are the key differences

between that what are the levels under

it like namely of course non-functional

is not a part of our labus you should

not break your head for getting into

what is performance testing what is

security testing Etc but at this point

all you should know is that what is the

difference between functional and

non-functional the levels what we have

covered in our syllabus are all

functional then we also differentiated

between white box and black box testing

approaches for dynamic testing and

Confirmation and regression testing

where confirmation is just like

retesting okay on the other hand of

course we also had a small topic here to

talk about was maintenance testing we

told you maintenance testing in turn is

regression testing and it helps you uh

measure the side effects of a change

every time you make an update upgrade

migration or retirement of the product

so put together this basically completes

our understanding on the chapter 2 given

that you know all these keywords and

differences between them then chapter 2

is well done for all of us moving on to

the Chapter 3 of course chapter 3 was

talking about static testing and the

concepts related to that of course at

this point we understood that not

everything gets done just with help of

dynamic testing there are several other

activities which do happen prior to

Dynamic testing and uh every single work

product should be a good candidate for

static testing because a human is error

prone and you can make mistakes thus

reviewing any work product which is

written by any individual is a good

practice in terms of process improvement

work product Improv ment and minimizing

your own mistakes which in turn gives

you a better quality of product at the

same time it helps you increase the

productivity of testing and development

in simple words if I try to eliminate

the defects from requirement when they

are gathered then I'll be more

productive in development rather finding

silly defects right or getting stuck for

silly defects so there's a whole bunch

of things which we of course discussed

in detail there so this particular

chapter drives you first through what is

static testing don't forget there are

two different ways to do static testing

reviews and static analysis the

documents which are readable by human

being and can be evaluated by going

through you call this or this call this

approach as review when you go through

the document and read it yourself and

review them but on the other hand uh

there are certain work products like

code or data flow diagrams and control

flow diagrams which might not be

manually valuable so you need a tool to

do this job for you and that's where a

static analysis comes into picture so in

simple word the V products which are

reviewed by Human by reading them we use

review and work products which are

reviewed by Tool we call it a static

analysis so here we also covered what

are the work products which are

candidate off review that means almost

anything as a document should be a

review candidate uh we also highlighted

here in one of the sections that what

are the differences between static and

dynamic testing so you must go through

that the list of common static defects

and plus we we also spoke about

something called as early and frequent

feedback which is very crucial for

someone to know from uh presentation of

your work to back to the business at a a

defined Milestone so that uh you are

aligned to that of the business

requirements but not getting deviated

from that so in aile methodologies we

present demonstrations to the customer

to make sure that they uh really get to

see what exactly we are building and if

in case we're getting deviated they can

let us know about it so early and

frequent feedback is very important

which we do worry about at the same time

uh we do uh saw the list of we did see

the list of uh the those common defects

which can be easily found by Static

testing when compared to that of dynamic

testing on the second side there the

second section of this chapter we

covered things related to review process

we spoke about the formal review process

which is a five-stage process consisting

of planning initiate review individual

review which is individual preparation

then communication analysis which is

also called as review meeting and then

we also spoke about the last one that is

fixing and Reporting this formal review

process consists of six standard roles

that is manager moderator review leader

reviewers scribe and uh the author the P

the person who has written the document

under review and responsible for fixing

it so make sure that you know the

process the activities under each of the

pH the roles and the responsibilities of

the roles because generally here we

expect match the following one side

they'll give you the review phases one

side they'll give you the activities of

it or they will give you the roles and

responsibilities of it and need to find

the right match of it same thing will

happen in the next segment which is the

review types we covered about informal

we covered about walkth through

technical review and inspection

inspection is as equal to your formal

review process so unique points have

been shared there so make sure that you

remember them at any point of time time

all you need to do is match the

following again so they will give you

the four review Types on one side and

they will give you the unique points on

one side or other forms of asking the

same thing but as far as you remember

the uniqueness of each type of review

you can differentiate between any two

reviews so that's the key thing and uh

we also covered the success factors

related to review which makes it very

crucial sometime they may give you

something out of the uh options or

examples given to you but all you have

to judge is Will this help me make a

review successful or will this be a

negativity to destroy the review so

that's how you can easily make a

judgment that which of this option is a

success factor for the review see the

syllabus is not about by Harding it

never do that it's not going to work out

let me tell you very clearly all you

need to do is understand it understand

in a way that you are going to apply it

in your day-to-day world and as you

apply them or you learn it in this

fashion you would always be able able to

crack the examination in single goal you

don't have to byard the things or

remember them you have to understand

what I'm trying to do and chapter 3 is

going to be slightly critical the only

reason is these are something which

doesn't happen in day-to-day basis in

most of the organization it does happen

in many organization but not quite often

so this is something which is going to

be slightly new and things which you

have never learned before well moving on

to the chapter four of course this

chapter is talking about the test

analysis and designed approaches or

techniques of course first we covered

the techniques uh we introduced you to

the three categories in the very first

section that what is blackbox testing

techniques what is white box testing

techniques and what are experience-based

test techniques quick reminder you need

to remember the basis of each of these

category like for blackbox we need

requirements or we refer requirements to

apply them if you don't have

requirements you cannot apply them then

same way for white box the basis is code

if you don't know how to read a code you

cannot apply white box and experience

phase is all about experience which

includes the past experience of testing

similar products the domain knowledge

where the product belongs and knowledge

of typical defects makes it all together

to be called as experience if you are a

fresh engineer you are not called as an

experienced tester and you cannot apply

these techniques so that's crucial

because sometimes they just get one

question directly from here asking you

which one of the following is one of the

basis for white box testing then you

must not be puzzled there then we went

into each of these uh for example in the

blackbox we covered equivalence

partition in equivalence partition we

covered single input double input single

input may be simple but double input

sometime can be a little tricky so make

sure that you just have a look once

again that what is the context I

mentioned there the detail I mentioned

to track or come to a conclusion that

what should be our

uh the two input combination so remember

one thing you have to minimize the test

cases with covering each class at least

once that's the statement we went to the

bva in BV we covered again two types of

it that is twoo analysis threo analysis

so please be cautious in the examination

question that which one they are asking

you to apply sometime they can even ask

you to combine EP and bva and ask you a

question together then we went through

decision table testing which is going to

be slightly simpler than the other two

because the table will be provided and

you will be asked a question related to

that but don't forget the

characteristics the slide deck has some

key pointers and those pointers are very

important to be remembered because

sometime they just ask you a theoretical

question about the technique

characteristics same thing applies to

State transition testing that is how do

you identify a valid transition how do

you identify invalid transition then STD

shows only valid transition so these are

some statements which I have specified

very clearly and sometime you do get a

theoretical question there or of course

the diagram driven then you know how to

identify the same based on those those

information itself moving on to the

white box we covered four parameters

there with two techniques the techniques

what we covered was statement testing

and Branch Testing where Branch Testing

is also called as decision testing so

never be you know ignoring the synonyms

of any terminology because istqb when

they give synonyms it means that they

can use any of the terms okay so

statement testing and Branch Testing um

and at the same time we covered

statement coverage and Branch coverage

so testing that is statement testing and

branch testing are the techniques to

find minimum number of test cases

whereas if your team says we did not use

the technique but have written some test

cases then how to measure the coverage

is done by The Matrix so statement

coverage and Branch coverage are the

matrices which we basically use to

measure the required coverage or the

coverage achieved by the written test

cases without the technique so both are

two different aspects of a process at

the same time this is at K2 so you don't

really have to break your head to

understand the process like how to solve

it but anyways in my tutorials I've

already covered that okay which will be

helpful and third category was

experience-based test techniques where

we covered error guessing exploratory

testing and checklist based testing all

three depends on the common basis that

is experience but has something unique

about itself error guessing has a

terminology fault attack exploratory

testing talks about test based sessions

test Charter are important and mandatory

there debriefing session is a method

used for reporting and exploratory is

not about randomly licking on the

application right so we just really need

to be careful with all those keywords

what you learn in every single technique

checklist based testing is all about

checklists the checklist uh certainly

contains questions which you need to

answer while interacting with the

product or testing the product uh but

the only challenge with the checklist is

that it is generally out of date so it's

very important to maintain it time to

time then we went to the last segment of

this which is uh certainly to talk about

the test analysis approaches and here we

covered things like what is

collaborative user story writing what

are the template of user story writing

and then we covered about acceptance

criteria how acceptance criteria can be

written there are standard formats for

it like given when then or in the

bulleted form or in the tabulated form

and so on and then we also covered a

complete process of what is acceptance

test driven development how exactly does

that happen and how test cases are

derived from acceptance criteria and

then the development kicks off so put

together chapter 4 is going to have a

very good contribution to your overall

success moving on to the next chapter

the chapter five the chapter five

certainly had another major aspect of

the entire testing to be discussed so

the journey starts with the basics which

is uh the test management all together

which are the common test activities

like what is test planning what is uh

the test estimation what is test

matrices or if you talk about entry

criteria exit criteria and few other

things there to deal with h of course we

went through a lot of things like test

execution schedule uh which talks about

the order of execution and and uh right

there we also discussed uh the

monitoring and control we told you again

that monitoring is a process of tracking

the ongoing progress with help of

matrices you saw some example of the

matrices at the same time you understood

what is just control control here means

If You observe a deviation from the plan

how exactly you can take an appropriate

control action to overcome the deviation

and conclude about it at the same time

uh of course we went through the

understanding of the overall process

that was what are those you know

estimation methods so we covered four of

them we had estimation by ratios extrap

extrapolation then we have White Band

delie and three-point estimation so

someone should really be aware of all

these things which are required at that

point of time so that's some of the

things what we covered initially then we

of course went through the risk

management which is another major

chapter to talk about or major segment

to talk about we covered about risk

identification risk assessment risk

mitigation and risk control which is

risk management alog together so we must

know the examples of project risk and

product risk from here should be able to

differentiate between them and what

exactly are the action items as a result

of risk mitigation not everything is

accepted sometime risk are mitigated

transferred and or deals with

contingency then we also covered a topic

on configuration management the key

important thing you should remember the

configuration management is all about

Version Control unique identification

traceability and managing the history of

revisions this particular thing is not

done manually it's very hectic to do so

we take tool support for this and given

that we do it tool support this is the

only tool which gets rolled out in the

beginning of the project all other tools

gets rolled out during test

implementation so if you remember that

you know everything about it right then

of course we went through the defect

management the defect management

discussed about what is defect which is

covered in chapter one itself but here

we covered about the defect reporting

which is what is the objective of

writing a defect report and at the same

time what does the defect report consist

of so put together that basically covers

everything what we need to know from the

chapter 5 and again has a great

contribution to add overall value to the

entire thing and finally to talk about

the chapter six which is uh another

crucial aspect of it of course chapter 6

talks about the test Tool uh however

it's a very small small chapter but yet

important to save your day at any point

of time so chapter six gave you an

introduction to what is test tools what

type of different test tools do we have

and uh at the same time what are the

benefits and risk involved in using a

tool so again just three topics to talk

about if you just remember the types of

tools you know about the benefits and

the risk involved in using a tool you

are pretty much good with this

particular chapter Al together so yet uh

it's just a small one but not something

which you can see as an optional because

those two marks could be a really

booster in your bad times so we would

strongly recommend that you do not

ignore this chapter because nothing is

optional here so in this particular

tutorial we just wrapped up everything

in the entire syllabus uh in just a

small video but yet important to recap

revise what the summary of this entire

syllabus is all about at the same time

at the end we would like to give you the

breakup of the questions because it

sometime becomes very important for some

people to really know that how the

contribution of each chapter would be in

my examination so just fulfilling that

uh expectation of all our Learners as

well so the breakup of the question as

you know that total number of questions

are 40 that is 40 and the breakup is

chapter 1 will have eight questions out

of 40 chapter 2 will have six questions

out of 40 chapter three will have four

questions chapter 4 will have 11

questions chapter five will have nine

questions

and chapter six will have two questions

so that's the breakup of the questions

and the weightage of each chapter in the

examination so as we see that all the

chapters are equally important I would

never discriminate any chapter here but

on a higher note I would see chapter 1

chapter 4 and chapter 5 are very

critical to save your day in fact

chapter four and five together forms 20

marks that is chapter 4 has 11 questions

and chapter five has nine questions so

20 marks lies just in these two chapters

and then then eight marks in write

chapter one then of course other 10

marks are with uh chapter 2 and three

but two marks with chapter 6 as well so

that's the breakup of course you can

plan your preparation accordingly and

you know that way you cannot leave a gap

right chapter 6 is anyway small so you

don't have a provision to leave a gap

but when it comes to chapter 1 chapter 4

and chapter 5 there should be no such

word which you do not know make sure

that you are going through everything in

that context or that particular way or

approach so put together I think this

basically helps us to understand how

this entire syllabus is drafted how this

entire examination works and don't

forget uh probably in the introduction I

forgot to mention that some of the

questions which is like one or two

questions will even have five options

and you'll be asked to select two of

them okay you will be asked to select

two of them as the right answers so

remember in this case you will be having

five options and whenever you see five

options make sure you select two answers

and you'll have check boxes if you're

appearing online so you have to select

two of them and both of them have to be

correct to get one Mark if anyone goes

wrong then you are partially incorrect

which means you are not sure about this

concept and that's where you don't get

any marks so there is no half marks for

this particular examination okay so put

together that summarizes our entire

journey of this particular syllabus and

this particular certification so that's

all from this particular tutorial team

wishing you all the very best for your

preparation and the examination you know

what exactly to do feel free to let me

know if you have any questions any

queries any doubts and any

clarifications I'm always here to

address your queries and answer them

well till then keep learning keep

exploring keep understanding the context

thanks for watching the video team and

happy learning

[Music]