javabyKiran Manual Testing call : 8888809416

Test Case Writing / Test Scenarios /Use cases

• What would be flow for writing test cases.?

• QA team receives BRD [Requirement Document]
• Once BRD is received Team lead will be creating Test plan
• QA engineers start writing use cases some time we write directly scenarios.
• Once Use cases finished, Scenarios will be written on the basis on Use cases.
one use case can have multiple scenarios.
• For every scenario we start writing a Test case. One scenario can have multiple
Test cases.
• One test case has multiple test steps.

• What is a Test Scenario?

o A test scenario, sometimes also called a scenario test, is basically a documentation of
a use case. In other words, it describes an action the user may undertake with a
website or app. It may also describe a situation the user may find themselves in while
using that software.
o Since test scenarios must ideally be approved by business analysts, developers, and
potential customers (a control group, ideally), they would really cover everything that
needs to be tested before the software goes public

• What is test case?

o Test cases are the step wise description or activities which are going to be executed to
validate the application. The test cases will contain the step number, description, or
activity - what action is going to happen while validation, the input data, the expected
result and the actual result. The test cases are written based on the functionality or
requirements, or the use cases received from the client. Test Cases will be prepared
by Testing Team.

Javabykiran.com 1
javabyKiran Manual Testing call : 8888809416

• What is test data?

o Test data is the data that is used in tests of a software system. To test a software
application, you need to enter some data for testing most of the features. Any such
specifically identified data which is used in tests is known as test data.
o You can have test data in excel sheet which can be entered manually while executing
test cases or it can be read automatically from files (XML, Flat Files, Database etc.)
by automation tools.

• Why we write test Cases

o To require consistency in the test case execution
o To make sure a better test coverage
▪ for this, we should cover all possible scenarios and document it, so that we
need not remember all the scenarios again and again.
o It depends on the process rather than on a person
▪ A test engineer has tested an application during the first release, second
release, and left the company at the time of third release. As the test engineer
understood a module and tested the application thoroughly by deriving many
values. If the person is not there for the third release, it becomes difficult for
the new person. Hence all the derived values are documented so that it can be
used in the future.
o To avoid training for every new test engineer on the product
▪ When the test engineer leaves, he/she leaves with a lot of knowledge and
scenarios. Those scenarios should be documented so that the new test
engineer can test with the given scenarios and can write the new scenarios.

Javabykiran.com 2
javabyKiran Manual Testing call : 8888809416

• Test Case template

Every website and study material might have different templates but some of the fields are constant.
• Testcase Id
• Test Scenario
• Test Case description
• Precondition
• Test Steps
• Test data
• Expected result

• Writing Good Test Cases

1. As far as possible, write test cases in such a way that you test only one thing at a
time. Do not overlap or complicate test cases.
2. Ensure that all positive scenarios and negative scenarios are covered.
3. Language: Write in simple and easy to understand language.
4. Use active voice: Do this, do that.
5. Use exact and consistent names (of forms, fields, etc.).

• Characteristics of a good test case:

a. Accurate: Exacts the purpose.
b. Economical: No unnecessary steps or words.
c. Traceable: Capable of being traced to requirements.

Javabykiran.com 3
javabyKiran Manual Testing call : 8888809416

d. Repeatable: Can be used to perform the test over and over.

e. Reusable: Can be reused if necessary

• Test Case Techniques [Important ]

f. Equivalence Partioning (EP)
g. Boundary Value Analysis (BVP)
h. Error Guessing

1. Equivalence Partioning (EP)

• EP divides the input data of a software unit into partitions of
equivalent data from which test cases can be derived
• Test cases are designed to cover each partition at least once. This
technique tries to define test cases that uncover classes of errors,
thereby reducing the total number of test cases that must be
developed.
• An advantage of this approach is reduction in the time required
for testing a software due to lesser number of test cases.
2. Boundary Value Analysis (BVP)
a. Tests are designed to include representatives of
boundary values
3. Error Guessing
• The Error guessing is a technique where the experienced and
good testers are encouraged to think of situations in which the
software may not be able to cope.
• The success of error guessing is very much dependent on the skill
of the tester, as good testers know where the defects are most
likely to be. Therefore, an error guessing approach, used after
more formal techniques have been applied to some extent, can be
very effective.

Javabykiran.com 4
javabyKiran Manual Testing call : 8888809416

• Types of Test Cases

i. Functional Test Cases: The test cases based on functional requirement
specifications
ii. Positive Test Cases: Test Cases with valid input and verifying that the
outputs are correct.

iii. Negative Test Cases: This testing involves exercising application

functionality using a combination of invalid inputs, some unexpected
operating conditions and by some other “out-of-bounds” scenarios.
iv. Non Functional Test Cases: The test cases based on
functional requirement specifications like performance,
Load, Stress, Security, etc.

• How to write the functional test cases

o In the expected results column, try to use should be or must be.
o Highlight the Object names.
o We must describe only those steps which we required the most; otherwise, we do not
need to define all the steps.
o To reduce the excess execution time, we will write steps correctly.
o Write a generic test case; do not try to hard code it.

• How to write the integration test cases

o Firstly, understand the product
o Identify the possible scenarios
o Write the test case based on the priority
When the test engineer writing the test cases, they may need to consider the following
aspects:
o If the test cases are in details:
▪ They will try to achieve maximum test coverage.
▪ All test case values, or scenarios are correctly described.
▪ They will try to think about the execution point of view.
▪ The template which is used to write the test case must be unique.

Javabykiran.com 5
javabyKiran Manual Testing call : 8888809416

• System test cases

▪ We will write the system test cases for the end-to-end business flows. And
we have the entire modules ready to write the system test cases.

• Test Case Review:

i. Reviewing is a form of testing too – the verification part of the V&V, also called
static testing.

Why Review: For the same reason we test the software

• To uncover errors
• To check for completeness
• To make sure the standards and guidelines are followed
Review Checklist:
• Do test cases cover all requirements?
• Has each test case been assigned a test case identifier?
• Does each test case specify?
- Actions
- Test condition
- Expected result
• Have the expected results been recorded in detail?
• Is any method for validating expected results specified?

• Do test cases for field validations, record validations

and database updates include the following?
- Valid conditions
- Invalid conditions
- Boundary or unusual conditions
• Do the test cases for reports include the test data along with the expected
output?
• Have the inter test case dependencies been described?
• Have Pass/Fail criteria been specified?
• Have all requested environments been specified?
• Has the method for logging on to the test environment been specified?

Javabykiran.com 6
javabyKiran Manual Testing call : 8888809416

• Are pre-conditions for the test specified?

• Is the number of Test cases met customer standards?

Javabykiran.com 7