ISTQB FOUNDATION 4.0 | Tutorial 46 | Entry Criteria & Exit Criteria | Test Management | CTFL

Summary

This tutorial delves into the ISTQB Foundation Level certification, specifically Chapter 5 on managing test activities. It focuses on the critical planning phase aspect of establishing entry and exit criteria. These criteria serve as checklists dictating the commencement and conclusion of tasks, applicable across projects, development, design, and testing processes. The tutorial emphasizes their importance in preventing oversights that could lead to costly delays. It provides examples of criteria and clarifies that they are tailored to organizational needs, not standardized. The script also connects traditional and Agile methodologies, equating entry criteria with 'Definition of Ready' and exit criteria with 'Definition of Done', crucial for Agile sprints.

Takeaways

• 📚 Entry and exit criteria are essential checklists that determine when to start and stop activities in various phases of projects, including testing.
• 🔍 These criteria are not limited to testing and can be applied to projects, development, design, and other processes.
• 🛠 Creating entry and exit criteria helps in ensuring that all prerequisites are met before starting a phase, preventing blockers and rework.
• 🗂 Entry criteria are preconditions that must be met before beginning a phase or activity, ensuring a smooth start.
• 📉 Exit criteria are measures that confirm the completion of an activity, allowing for a successful conclusion and transition to the next phase.
• 💡 The importance of these criteria lies in preventing time and cost wastage by ensuring all necessary steps are taken before proceeding.
• 📝 Examples of entry criteria include the availability of resources, testware, and initial quality levels, which are crucial for starting a test phase.
• 📊 Exit criteria may include achieving a required level of coverage, having a limited number of unresolved defects, and ensuring all tests have been executed or reported.
• 🔑 Entry and exit criteria are driven by organizational or project specifications and cannot be standardized across all projects.
• 🔄 In Agile methodologies, entry criteria are referred to as 'Definition of Ready' and exit criteria as 'Definition of Done', guiding when to start and stop sprints.
• 📈 Remember that entry criteria focus on predictions and prerequisites, while exit criteria deal with actual completion and outcomes.

Q & A

What is the main focus of the tutorial in the provided transcript?

The tutorial focuses on explaining the concept of entry and exit criteria in the context of test planning and their importance in various phases of a project or testing process.

Why are entry and exit criteria important in project management?

Entry and exit criteria are important because they ensure that all prerequisites are met before starting a phase and that all objectives are completed before ending a phase, preventing blockers, rework, and waste of time and resources.

What does the term 'entry criteria' refer to in the context of testing?

Entry criteria refer to a set of activities or conditions that must be performed or met before starting a specific phase, test level, or the entire testing process.

Can entry and exit criteria be standardized across different projects?

No, entry and exit criteria are not standardized and are driven by the organization's or project's specific requirements and objectives.

What is an example of an entry criterion in a testing project?

An example of an entry criterion could be the availability of resources such as people, tools, environments, test data, budget, and time.

What is an example of an exit criterion in a testing project?

An example of an exit criterion could be achieving a certain level of test coverage, such as 90% code coverage, as agreed upon with the business.

How do entry and exit criteria relate to the Agile methodology?

In Agile methodology, entry criteria are often referred to as 'Definition of Ready' (DoR), indicating when a task or feature is ready to be started, while exit criteria are called 'Definition of Done' (DoD), indicating when a task or feature is considered complete.

What is the purpose of conducting smoke or sanity tests as part of the entry criteria?

Smoke or sanity tests are conducted to ensure that the initial quality level of the test object is acceptable before正式启动testing activities, thus serving as a preliminary check to avoid major issues down the line.

What are some factors that might be included in exit criteria to determine if testing is complete?

Factors that might be included in exit criteria could be thoroughness of testing, achieving required levels of coverage, the number of unresolved defects being within an acceptable limit, and the completion of all planned tests.

How do entry and exit criteria help in managing the testing process?

Entry and exit criteria help in managing the testing process by providing clear guidelines on when to start and stop testing activities, ensuring that all necessary steps are taken and that the testing is completed as per the defined objectives.

What is the significance of having clear entry and exit criteria in the context of a testing project?

Having clear entry and exit criteria ensures that the testing process is systematic and goal-oriented, preventing the project from starting without necessary preparations and from ending without achieving the desired outcomes.

Outlines

00:00

📘 Introduction to Entry and Exit Criteria in Test Planning

The first paragraph introduces the concept of entry and exit criteria within the context of test planning for ISTQB Foundation level certification. It emphasizes the importance of these criteria as checklists that determine when to start and stop activities, not just in testing but across various stages of a project. The speaker explains that entry criteria are prerequisites that must be met before beginning any phase, while exit criteria confirm the completion of tasks. The paragraph also highlights the significance of these criteria in avoiding rework and ensuring a smooth workflow, with examples provided to illustrate their application.

05:00

📚 Detailed Explanation of Entry and Exit Criteria with Examples

The second paragraph delves deeper into the specifics of entry and exit criteria, providing examples and explaining their role in different testing methodologies. Entry criteria might include the availability of resources such as people, tools, environments, test data, budget, and time, as well as the initial quality level of the test object. Smoke or sanity tests are mentioned as a common entry criterion to ensure build acceptance. For exit criteria, the paragraph discusses measures like requirement coverage, code coverage, and the number of unresolved defects, which determine if testing can be concluded. The speaker also connects these criteria to Agile methodologies, where entry criteria are known as 'Definition of Ready' and exit criteria as 'Definition of Done', emphasizing their importance in sprint planning. The paragraph concludes by advising that the exact criteria should be tailored to the specific needs and objectives of the project or organization.

Keywords

💡ISTQB Foundation Level Certification

The ISTQB Foundation Level Certification is an international standard for software testing professionals. It ensures that individuals have a foundational understanding of software testing principles and practices. In the video, this certification is the subject of the tutorial series, with the current chapter focusing on managing test activities, emphasizing the importance of understanding the certification's content for a career in software testing.

💡Test Planning

Test planning is the process of defining the activities, resources, and schedule for delivering a testing process. It is a critical phase in the software development life cycle, ensuring that testing is conducted methodically and effectively. The video discusses test planning as part of chapter 5, highlighting its significance in setting the stage for successful test execution.

💡Entry Criteria

Entry criteria are preconditions that must be met before starting a particular phase, test level, or the entire test process. They act as checklists to ensure that all prerequisites are in place to begin work smoothly. In the script, entry criteria are discussed as essential for avoiding blockers and rework, with examples including resource availability and initial quality levels of the test object.

💡Exit Criteria

Exit criteria define the measures and checks that determine when an activity or phase is considered complete. They ensure that all objectives have been met, and it is appropriate to conclude the testing process. The video script uses examples such as achieving a required level of coverage and the number of unresolved defects to illustrate how exit criteria are used to signal the completion of testing activities.

💡Checklists

Checklists in the context of the video refer to the systematic lists of items or tasks that need to be verified or completed. They are crucial for both entry and exit criteria, helping to ensure that nothing is overlooked during the start or end of testing phases. The script emphasizes the importance of checklists for preventing time and cost wastage.

💡Resource Availability

Resource availability is a key entry criterion that includes the readiness of people, tools, environments, test data, budget, and time. The script mentions resource availability as an essential factor for kickstarting work, indicating that without the necessary resources, the testing process cannot commence effectively.

💡Testware

Testware encompasses all the work products used for testing, such as test bases, testable requirements, user stories, and test cases. The script discusses testware as a critical component of entry criteria, suggesting that having testware ready is essential for starting the testing process.

💡Coverage

Coverage in software testing refers to the extent to which the software has been tested against the specified criteria. The script mentions various types of coverage, such as requirement, code, functional, and decision coverage, as part of the exit criteria, indicating that achieving agreed-upon levels of coverage is necessary to conclude testing.

💡Defect Density

Defect density is the number of defects found per unit of software measure, such as per thousand lines of code. In the context of exit criteria, the script mentions defect density as a metric that needs to be within the thresholds defined in contracts and service level agreements, signifying that a certain quality standard must be met before testing can be considered complete.

💡Regression Testing

Regression testing is the process of re-running existing tests to ensure that changes to the code have not introduced new defects. The script discusses regression testing, particularly automated regression tests, as a deliverable at the end of a project, indicating that having a regression test suite in place is part of the exit criteria for ensuring software stability.

💡Agile Methodologies

Agile methodologies, such as Scrum and Kanban, are iterative and incremental approaches to software development that emphasize flexibility and collaboration. The script connects entry and exit criteria with the Agile concepts of 'Definition of Ready' and 'Definition of Done,' respectively, illustrating how these criteria are adapted in Agile environments to determine when work can begin and when it is complete.

Highlights

Introduction to managing test activities in ISTQB Foundation Level certification, Chapter 5.

Focus on 5.1, discussing test planning and the importance of entry and exit criteria in the planning phase.

Entry and exit criteria are not limited to testing; they can be applied across projects, development, design, and more.

Definition of entry criteria as a set of activities that must be performed before starting a phase or test level.

Importance of creating checklists to avoid forgetting critical steps that could lead to delays and increased costs.

Exit criteria as a checklist that determines when an activity or phase is considered complete.

Examples of entry criteria including resource availability, budget, time, environment, and testware.

Entry criteria also involves conducting initial quality checks like smoke or sanity tests before starting.

Exit criteria examples include achieving required coverage levels, resolving a certain number of defects, and meeting defined thresholds.

Exit criteria also involves ensuring all planned tests are executed, defects are reported, and regression tests are automated.

Customization of entry and exit criteria based on organizational or project specifications, with no standardized approach.

Explanation of how entry and exit criteria relate to 'Definition of Ready' and 'Definition of Done' in Agile methodologies.

Clarification that entry criteria are preconditions for starting an activity, while exit criteria define completion measures.

Highlighting the importance of tailoring entry and exit criteria to the specific objectives of each test level.

Emphasis on the practical application of entry and exit criteria to ensure smooth project progression without blockers.

Encouragement for viewers to explore and understand the context of entry and exit criteria in their own projects.

Invitation for viewers to comment with questions for further discussion and clarification.

Closing remarks with a motivational note to keep learning and exploring in the field of software testing.

Transcripts

Hello friends and greetings for the day

welcome back to another tutorial on

istqb Foundation level certification we

are in chapter 5 talking about managing

the test activities and continuing ahead

with 5.1 that is test planning and today

we shall be talking about another

important aspect of planning phase that

is what is entry and exit

criteria

in order to talk about entry and exit

criteria we need to really understand

that these are these These are those

checklists which basically determine

when you can start something and when

you can stop something when I use the

word something certainly I mean it that

means entry and exit criteria are not

test related artifacts alone it can be

used for a project it can be used in

development it can be used in design it

can be used for entire testing process

or it can even be used for test

activities or test levels and even test

phases like test planning design

execution Etc so entry and exit

criterias are not limited to those of a

particular test level itself it can be

used wherever you think it is important

for you to take care of certain you know

specific things like prerequisits and

those checks what you really need to

perform before you say you are done yes

exactly that's what the definition of

entry and exit criteria is entry

criteria are set of those activities

what you must have performed or should

have performed before kick starting with

any particular phase or test level or

maybe even the test process entirely now

the question is why should I create

these checklists are they really

important answer is exactly it is very

important in terms of not forgetting

anything before you get started because

if you forget anything all the way down

the line when you remember about it you

may be having a stopper blocker or you

may have to hold or probably redo it in

terms of wasting your time and money

both right so as simple as when you're

planning for a trip and if you forget

something to carry along with you either

you have to come back to pick it up or

you may have to buy another at the

destination in both the cases either you

are investing your time which is

precious and either you're investing

your cost which is buying another one

which will be useless when you come back

right so exactly with the same motive we

talk about creating an entry and exit

criteria just to make sure that

everything is fulfilled and we start

smoothly without any kind of deviations

and blockers on our activities and same

way on the other side exit criteria is a

checklist which contains those measures

and those checks which determines you

have done what you were supposed to do

and you can happily stop now and head

over to the business so in this

particular tutorial we'll be looking at

some of the quick examples to get some

insights about hey what can I include in

entry and exit criteria but most

importantly please remember entry and

exit criterias are completely driven by

the organizations or the project

specifications and it's not something

which can be standardized so please

remember the examples what we are giving

you are just for your kind information

but organization have complete freedom

to decide what should be their entry

criteria and exit criterias so let's

look at the quick definitions what the

cabus is trying to talk talk about that

is entry criteria defines the

preconditions for undertaking a given

Act activity if entry criteria are not

meant it is likely that the activity

will prove to be more difficult time

consuming costly and sometime even

riskier on the other hand exit criteria

determines what must be achieved in

order to declared an activity completed

entry criteria and exit criteria should

be defined for each test level and will

differ based on their objectives so that

certainly clarifies that what exactly is

the definition of Entry and exit

criteria now let's quickly have a look

on some of these samples to understand

it better so when it comes to entry

criteria a typical list of Entry

criteria may be related to like

availability of resources for example if

I talk about the people the tools

environments test data budget and time

as soon as I have the required resources

I can Kickstart that work as I have the

given schedule defined I can know what

exactly is the date to Kickstart or even

if I talk about environment availability

I may get started with the test

execution phase so if you notice the

examples are from different aspects the

levels the phase the process like budget

and time is more from the process point

of view and environment is more from a

phase point of view like test execution

similarly another one is availability of

testware which could be also related to

all the faces what we may have or test

levels what we conduct like test bases

testable requirements user stories and

test cases plus to add here the initial

quality level of the test object like if

you have to conduct any smoke tests you

can certainly do them in order to accept

the build in order to get started so yes

conducting smoke or sanity test as a

practice certainly determines that it is

one of the entry criteria to get started

with the process on the other hand if I

talk about the exit criteria these are

the checklist which contains the items

which does the torous measures or those

checks which determines the job is done

so the examples include of thoroughness

which includes achieving level required

level of coverage like this could be

requirement coverage code coverage

functional coverage decision coverage

which the business and you have agreed

upon so say for example the business

said I want 90% uh code coverage at

least in order to release the product

then it should not be 9 then you have to

do 1% more in order to stop the testing

also to add further the number of

unresolved effect is one of of the

important parameter to make sure that

the defects which are uh open uh should

be in the greed limit and then def

density number of fail test cases how

many they should be what are the

threshold defined in the contract and

slas you may have to take into account

talking about the completion criterias

criteria they do include things like

plan tests have been executed or not how

many are pending at any point of time

static testing has been performed all

defects found have been reported of

course I cannot make make sure that all

defects have been resolved because

sometime you do have a tolerance on

defects closure but at least reported

they have to be documented that there

are no such defects which are still on a

verbal note and also to talk about the

regression test are automated so

generally you know that regression test

are getting automated at the end of the

project as a deliverable to the business

so again they have their own aspect it's

not necessary that every single point

would make sense to any any particular

project you may have to still analyze

your own project and your activities

your objectives in order to make sure

what should be your precise entry and

exit criteria okay also to last but re

reconnect to the dots between the

traditional and the aile methodologies

many people quite often get confused

that okay what is definition of ready

and what is definition of done it's

exactly the same entry criteria is

called as definition of ready for us

print when it comes to hij methodology

and when it comes to exit credit

criteria we call it as definition of

done in aile methodology so entry and

exit are just called as DOD and do sorry

do and DOD when it comes to AAL

methodology and they are specifically

for the Sprints okay so Sprints when to

start when to stop I use definition of

ready and definition of done okay so

that's all to talk about entry and exit

criteria however in the examination they

can use any other type of examples as

well all you need to judge looking at a

point point is that will this start will

this help you to start something or is

this talking about you have done what

you were supposed to do okay so anything

which is kind of like predictions is

entry criteria anything which is talking

on actuals is exit criteria okay so

that's all from this particular tutorial

team should you have anything else feel

free to comment below I'm always there

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]