A test case specifies the inputs, the execution conditions, the testing procedure, and the expected results to describe a single test to be run for a particular software testing objective.
So while writing a test case in manual testing one should be aware of the components that are used to write a test case. Test cases have several components.
When writing a test case one should use the below-mentioned components as much as possible to ensure that a test case is easily understandable.
The title is the first component of a test case, it should be easy to understand, and the user should be able to understand the test scenario after reading the title.
This includes all the pre-requirements necessary for the test to be carried out.
The Test Steps are the steps that need to be performed to perform the scenario in a test case.
Once the test steps have been performed, define the result that should be displayed.
Test Data contains the data that is to be used for testing purposes. Such as:
A test suite is a set number of test cases, so while writing a test case make sure to create a test case in the correct suite. The suite here signifies the module for which the test case is written, so the test case should always be written in the correct suite.
Test case priority helps the user to understand in which order test cases should be executed.
This test case belongs to which component of the application or a test suite.
You can also add a few keywords to the test cases which can refer to the related defects or any other reference.
Screenshots and screencasts can be added to the test cases for training purposes or for finding the bugs in regression.