Scribd
Upload
63 views

Lab Assignment 8

This document provides guidance on developing and writing test cases. It defines a test case as a document used to develop test scenarios to verify if application features work as intended. Test cases contain preconditions, steps, expected results, and actual results. Developers typically write unit and integration tests, while testers focus on acceptance tests. The document then outlines a 9-step process for writing manual test cases, including assigning an ID, describing the test case, defining preconditions and steps, gathering test data, outlining expected and actual results, and determining the test status.

Uploaded by

Vaishnavi G 18CA248
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
63 views

Lab Assignment 8

This document provides guidance on developing and writing test cases. It defines a test case as a document used to develop test scenarios to verify if application features work as intended. Test cases contain preconditions, steps, expected results, and actual results. Developers typically write unit and integration tests, while testers focus on acceptance tests. The document then outlines a 9-step process for writing manual test cases, including assigning an ID, describing the test case, defining preconditions and steps, gathering test data, outlining expected and actual results, and determining the test status.

Uploaded by

Vaishnavi G 18CA248
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Vaishnavi G

MCA II Semester - Software Testing


Registration Number: EA2132251010004

Lab Assignment 8 : Develop Writing and Tracking Test Cases

Aim:

To Develop Writing and Tracking Test Cases

What is a Test Case?


A test case template is a document that comes under one of the test artifacts, which
allows testers to develop the test cases for a particular test scenario in order to verify
whether the features of an application are working as intended or not.
Test cases are the set of positive and negative executable steps of a test scenario which has
a set of pre-conditions, test data, expected results, post-conditions, and actual results.

Who Writes Test Cases?


It varies from company to company. Assuming that a team contains developers and
dedicated testers then it might be something like a joint effort.
Developers write Unit Tests
Developers & Testers write Integration Tests
Testers write Acceptance Tests

How To Write Test Cases in Manual Testing


Follow the below steps to write the test cases.

Step #1 – Test Case ID:


Each test case should be represented by a unique ID. It’s good practice to follow some
naming convention for better understanding and discrimination purposes.

Step #2 – Test Case Description:


Pick test cases properly from the test scenarios
Example:
Test scenario: Verify the login of Gmail
Test case: Enter a valid username and valid password

Step #3 – Pre-Conditions:
Vaishnavi G
MCA II Semester - Software Testing
Registration Number: EA2132251010004
Conditions that need to meet before executing the test case. Mention if any preconditions
are available.
Example: Need a valid Gmail account to do login

Step #4 – Test Steps:


To execute test cases, you need to perform some actions. So write proper test steps.
Mention all the test steps in detail and in the order how it could be executed from the end-
user’s perspective.
Example:
Enter Username
Enter Password
Click Login button

Step #5 – Test Data:


You need proper test data to execute the test steps. So gather appropriate test data. The
data which could be used an input for the test cases.
 Username: [email protected]
 Password: STM

Step #6 – Expected Result:


The result which we expect once the test cases were executed. It might be anything such as
Home Page, Relevant screen, Error message, etc.,
Example: Successful login

Step #7 – Post Condition:


Conditions that need to achieve when the test case was successfully executed.
example: Gmail inbox is shown

Step #8 – Actual Result:


The result which system shows once the test case was executed. Capture the result after
the execution. Based on this result and the expected result, we set the status of the test case.
Example: Redirected to Gmail inbox

Step #9 – Status:
Vaishnavi G
MCA II Semester - Software Testing
Registration Number: EA2132251010004
Finally set the status as Pass or Fail based on the expected result against the actual result.
If the actual and expected results are the same, mention it as Passed. Else make it as Failed.
If a test fails, it has to go through the bug life cycle to be fixed.
Example:
Result: Pass

You might also like