Test Case
To write effective test case I have few criteria
1- I put myself into customer shoes by writing
test scenarios by end users perspective
2-I am trying to be specific by using clear statements
to make it understandable by everyone
3-And I am aiming %100 test coverage by
planing my test cases to make sure covers each
component and functionality specified in SRS document
4-And also I actively use test case management tool
jiraxray which helps me not only write text effective
test cases but also helps me in tracking the progress about them
5-Also I try to keep the description small
simple and informative. Nobody likes to read long stories :)
6-And most importantly I try to do things differently
I try to think exceptionally.
4.67
3
HOW TO WRITE TEST CASES
I break down the process into small pieces.
1. Requirement Analysis: Process starts with the grooming meeting.
I listen my PO very carefully during the grooming meeting.
Because she knows all the system reqirements and has
connection with the business side. Even she knows all
expectations about the functionality she might not
reflect all details to the user stories and exceptance
criterias. So, I try to figure out what is the root
cause of any acceptance criteria. If I have some
doubts at first glance, it is high time to raise
some additional question to her to clarify in and out.
After grooming meeting, I have 3 days to digest
all user stories and acceptance criterias before
sprint planning meeting. I try to find the gaps and bugs
at these phase which is a kind of static testing.
So, I can throw more detailed question on Sprint Planning meeting.
The output of this phase is going to be RTM (Requirement Tracability Matrix).
2. Test Planning: The most important deliverable is the test plan.
In this document, we cover the scope of the test,
the test strategy, testing types and tools to be implemented,
roles and responsibilities. QA Lead prepares the
test plan on Jira and allocates the tasks for all QA team members.
She posts the Test Plan on Jira.
3. Test case development:
During this phase, I generate test cases for
each and every functionality, covered in RTM.
After writing my test steps I ask related developer
and PO to review my test steps just to make sure
that I cover all requirements and we are on the same page.
I always choose to start with happy path for each scenario.
Then I try to find out the limitations and boundries of
the functionality which I can extract from acceptance criteria.
I force the function against all type of limitations
with different scenarios. The last
I create some negative scenarios.
If I find any gap during this phase
I go and tell PO to add some additional
acceptance criterias or clarify them.
Thank you!
3
4.67
(3 Votes)
0
0
0
HOW TO WRITE TEST CASES
I break down the process into small pieces.
1. Requirement Analysis: Process starts with the grooming meeting.
I listen my PO very carefully during the grooming meeting.
Because she knows all the system reqirements and has
connection with the business side. Even she knows all
expectations about the functionality she might not
reflect all details to the user stories and exceptance
criterias. So, I try to figure out what is the root
cause of any acceptance criteria. If I have some
doubts at first glance, it is high time to raise
some additional question to her to clarify in and out.
After grooming meeting, I have 3 days to digest
all user stories and acceptance criterias before
sprint planning meeting. I try to find the gaps and bugs
at these phase which is a kind of static testing.
So, I can throw more detailed question on Sprint Planning meeting.
The output of this phase is going to be RTM (Requirement Tracability Matrix).
2. Test Planning: The most important deliverable is the test plan.
In this document, we cover the scope of the test,
the test strategy, testing types and tools to be implemented,
roles and responsibilities. QA Lead prepares the
test plan on Jira and allocates the tasks for all QA team members.
She posts the Test Plan on Jira.
3. Test case development:
During this phase, I generate test cases for
each and every functionality, covered in RTM.
After writing my test steps I ask related developer
and PO to review my test steps just to make sure
that I cover all requirements and we are on the same page.
I always choose to start with happy path for each scenario.
Then I try to find out the limitations and boundries of
the functionality which I can extract from acceptance criteria.
I force the function against all type of limitations
with different scenarios. The last
I create some negative scenarios.
If I find any gap during this phase
I go and tell PO to add some additional
acceptance criterias or clarify them.
Thank you!
0
0
0
0
0
HOW TO WRITE TEST CASES
I break down the process into small pieces.
1. Requirement Analysis: Process starts with the grooming meeting.
I listen my PO very carefully during the grooming meeting.
Because she knows all the system reqirements and has
connection with the business side. Even she knows all
expectations about the functionality she might not
reflect all details to the user stories and exceptance
criterias. So, I try to figure out what is the root
cause of any acceptance criteria. If I have some
doubts at first glance, it is high time to raise
some additional question to her to clarify in and out.
After grooming meeting, I have 3 days to digest
all user stories and acceptance criterias before
sprint planning meeting. I try to find the gaps and bugs
at these phase which is a kind of static testing.
So, I can throw more detailed question on Sprint Planning meeting.
The output of this phase is going to be RTM (Requirement Tracability Matrix).
2. Test Planning: The most important deliverable is the test plan.
In this document, we cover the scope of the test,
the test strategy, testing types and tools to be implemented,
roles and responsibilities. QA Lead prepares the
test plan on Jira and allocates the tasks for all QA team members.
She posts the Test Plan on Jira.
3. Test case development:
During this phase, I generate test cases for
each and every functionality, covered in RTM.
After writing my test steps I ask related developer
and PO to review my test steps just to make sure
that I cover all requirements and we are on the same page.
I always choose to start with happy path for each scenario.
Then I try to find out the limitations and boundries of
the functionality which I can extract from acceptance criteria.
I force the function against all type of limitations
with different scenarios. The last
I create some negative scenarios.
If I find any gap during this phase
I go and tell PO to add some additional
acceptance criterias or clarify them.
Thank you!
0
0
0
0
0
HOW TO WRITE TEST CASES
I break down the process into small pieces.
1. Requirement Analysis: Process starts with the grooming meeting.
I listen my PO very carefully during the grooming meeting.
Because she knows all the system reqirements and has
connection with the business side. Even she knows all
expectations about the functionality she might not
reflect all details to the user stories and exceptance
criterias. So, I try to figure out what is the root
cause of any acceptance criteria. If I have some
doubts at first glance, it is high time to raise
some additional question to her to clarify in and out.
After grooming meeting, I have 3 days to digest
all user stories and acceptance criterias before
sprint planning meeting. I try to find the gaps and bugs
at these phase which is a kind of static testing.
So, I can throw more detailed question on Sprint Planning meeting.
The output of this phase is going to be RTM (Requirement Tracability Matrix).
2. Test Planning: The most important deliverable is the test plan.
In this document, we cover the scope of the test,
the test strategy, testing types and tools to be implemented,
roles and responsibilities. QA Lead prepares the
test plan on Jira and allocates the tasks for all QA team members.
She posts the Test Plan on Jira.
3. Test case development:
During this phase, I generate test cases for
each and every functionality, covered in RTM.
After writing my test steps I ask related developer
and PO to review my test steps just to make sure
that I cover all requirements and we are on the same page.
I always choose to start with happy path for each scenario.
Then I try to find out the limitations and boundries of
the functionality which I can extract from acceptance criteria.
I force the function against all type of limitations
with different scenarios. The last
I create some negative scenarios.
If I find any gap during this phase
I go and tell PO to add some additional
acceptance criterias or clarify them.
Thank you!
0
0
0
0
0
HOW TO WRITE TEST CASES
I break down the process into small pieces.
1. Requirement Analysis: Process starts with the grooming meeting.
I listen my PO very carefully during the grooming meeting.
Because she knows all the system reqirements and has
connection with the business side. Even she knows all
expectations about the functionality she might not
reflect all details to the user stories and exceptance
criterias. So, I try to figure out what is the root
cause of any acceptance criteria. If I have some
doubts at first glance, it is high time to raise
some additional question to her to clarify in and out.
After grooming meeting, I have 3 days to digest
all user stories and acceptance criterias before
sprint planning meeting. I try to find the gaps and bugs
at these phase which is a kind of static testing.
So, I can throw more detailed question on Sprint Planning meeting.
The output of this phase is going to be RTM (Requirement Tracability Matrix).
2. Test Planning: The most important deliverable is the test plan.
In this document, we cover the scope of the test,
the test strategy, testing types and tools to be implemented,
roles and responsibilities. QA Lead prepares the
test plan on Jira and allocates the tasks for all QA team members.
She posts the Test Plan on Jira.
3. Test case development:
During this phase, I generate test cases for
each and every functionality, covered in RTM.
After writing my test steps I ask related developer
and PO to review my test steps just to make sure
that I cover all requirements and we are on the same page.
I always choose to start with happy path for each scenario.
Then I try to find out the limitations and boundries of
the functionality which I can extract from acceptance criteria.
I force the function against all type of limitations
with different scenarios. The last
I create some negative scenarios.
If I find any gap during this phase
I go and tell PO to add some additional
acceptance criterias or clarify them.
Thank you!
0
0
0
4
1
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
1
4
(1 Votes)
0
0
0
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
4
8
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
8
4
(8 Votes)
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
0
0
It is documentation which describes step by step how to perform testing.
A Test Case contains test steps, test data, precondition,
postcondition developed for specific test scenario
to verify any requirement.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
0
0
0
5
2
What does Test Case consist of?
It is documentation which describes step by step how to perform testing.
It includes:
- test case ID (TC ID)
- test case name (TC Name)
- pre-condition
- step definitions
- test data
- expected/actual result
- pass/fail
Tester creates test cases.
Thank you!
2
5
(2 Votes)
0
Are there any code examples left?
New code examples in category Other
Relative searches
Writing of Test Cases
What is testcase and why we write test cases.
create test case
what is a test case for a program
What does a test case contain
how to write test cases in manual testing
writing test cases for manual testing
where to make test cases
test case definition
how test case looks like
for which case test case should be written
what is the test case and who we writes
test case for
writing test cases best practices
what Test case included
a sample of test case
test case is designed to
case testing
identify the thing which should not be test case
best practices writing test cases
test case desing
desinged test case
how to write test cases in testng
how to write test cases in software testing
when do we write a test case
test case meaning
a test case is
test case creation
define what a test case is
what is the test case
what is test case and how to write the test cases
how to write test that cover all cases
test case means
example of a test case
how to write equivalent test cases
sample testng test case
what i should be on test case
test case
what is test case with example
writing test cases software
test case defination
format of writing test cases
how to write test cases for manual testing
where to write test cases
how to create test case
what to write in test case
how to write manual testing test cases
how to write good test cases in manual testing
how to write test case
write test case
the test case
Test Cases writing i
what is test case used for
test case are designed during
how to make test case
writing test cases given when then
components of a test case
example of test case
writing the test cases
how to generate test cases
To Test software by developing various test cases for software project and practice it on the project
effective test cases
Write test cases around the result ranking criteria
the steps in a test case must be indented
how to prepare test cases
standard test case format
how to write manual test cases
test case sample
what is test case in software testing
EFFECTIVE TEST CASSE
how to write qa test
explain how to execute test cases
writing down test cases
Can you write a test case that verifies the behavior of submitting a form?
sample test cases
how to write a good test case
test cases example
valid test case
the components of a test case include the following. check all that apply
what does test case mean to tyou?
software testing test cases
manual test cases
Test project example
format in test case
test cases in software testing examples
test case writing
design test cases for given scenarios
test cases format
manual test case steps example
good test case
what test case should contains
what test case have
what test case consist of
which is used to create the test case for login
what are test cases in software testing
effective test case writing techniques
how to write test case exffectively
how to create test case exffectively
in software testing test case
what is meant by test case
test case in software engineering
test case example template
creating a test case document expected actual
qa where write test cases scenarios
test case document
use and test case
what is a test case in software testing
test cases document
how to make test cases for experienced testing
testcase meaning in cp
what is a test case
watch all true testcases
start writing test case from scratch
how to start writing test cases for web app
cses test case
find code for test cases
test case example
programming test case template
test cases in software testing
Which test cases are easy to identify?
manual test cases template
what is test case
testcase
test case requirements template
how to build test cases
how to make testcase past aT A specific condition
test case sample
test case ?
define a format of writing a good test case
test case requirements
test case examples
how to get the test cases for testing reporting in qa manual testing
writing quality test cases
writing test cases
How to wwrite a test case for a HTML file
testing case document
HOW TO ADD TEST CASES IN APP
test case
sample test script for software testing
writing test cases for project
how to write test cases
what does a test case consists of
how do you write test cases
how to write effective test cases
how to write a test case
effective test case
