Guidelines for Writing Test Cases, Software Testing Job Responsibilities, Derive Test Scenarios, Document Test Cases, and Collect Test Data.
Writing Test Cases is an important task in software testing, software testing job responsibilities are:
- Understanding & Analyzing software requirements.
- Derive Positive & Negative test scenarios.
- Document test cases.
- Collect test data.
- Execute test cases.
- Analyze test results.
- Report defects.
- Track defects.
- Re & Regression testing.
- Organize & Maintain software test resources.
Software Test Case Writing Guidelines
1. Automated Test case scope is more than Manual Test Case.
2. Test Data/Input is not required for every Test case in our project.
3. The completeness of Software Testing is Positive & Negative Testing.
4. Some Requirements may not have Negative scenarios.
5. Conducting Positive and Negative Testing.
6. Result Analysis is an important task in Performance Testing than Functional Testing.
7. In Manual Testing, we can write test cases using either an Excel file or a Test Management tool.
8. We derive Test cases from Requirements if follow sequential Software Development and User Stories for Incremental & Iterative development.
9. We collect Test data from different sources.
10. No Test case writing in informal testing.
1. Automated Test case scope is more than Manual Test Case.
Generally, we insert a single verification point in the Manual test cases as a human user can’t concentrate on multiple verification points at a time. We can insert multiple verification points in automated test cases, the test tool is software and it can verify multiple verification points at a time.
Note: Suppose if we have eight hundred manual test cases in a project, want to automate them, Eight hundred automated test cases are not required to automate those test cases, using three or four hundred automated test cases we can automate.
2. Test Data/Input is not required for every Test case in our project.
Input or test data is required only for test cases which are having input fields, and test data is not required for all test cases.
3. The completeness of Software Testing is Positive & Negative Testing.
We need to test all valid and invalid operations of the software application, so we conduct positive & negative testing.
4. Some Requirements may not have Negative scenarios.
Negative testing is not required for all software requirements, it is required only for some functionalities which are having input fields.
5. Conducting Positive and Negative Testing.
If test cases are having input fields then we conduct positive testing using valid input and conduct negative testing using invalid input. suppose if no input in any test cases then we use ‘incorrect expected result’ for negative testing.
6. Result Analysis is an important task in Performance Testing than Functional Testing.
In functional testing result analysis is simple, if a functional test fails then we can say that is the application defect, but if a performance test fails then we need to consider several factors for analyzing the result, that may be application performance issue or server response or network communicators issue.
7. In Manual Testing, we can write test cases using either an Excel file or a Test Management tool.
If you are using any test tool (Ex: ALM/QC or Jira) for test management to write manual test cases then we can use that tool provided test case template, and test cases can be stored in the tool database.
If you are not using any test tool for test management then you can use a spreadsheet like Excel to write the manual test cases.
Note: To write automated test cases, every test tool like UFT, RFT, JMeter, etc, provides an editor. API like Selenium (no IDE) you can use Eclipse IDE software to write test cases.
8. We derive Test cases from Requirements if follow sequential Software Development and User Stories for Incremental & Iterative development.
If we follow sequential software development (Ex: Waterfall or V model) then we derive test cases from ‘Software requirements’. Suppose if we use Incremental and iterative model (Ex: Agile model/s) for software development then we derive test cases from ‘User stories’.
9. We collect Test data from different sources.
We collect test data from different sources, we (testers) prepare some test data, collect some test data from the customer, and collect some test data from developers also.
10. No Test case writing in informal testing.
We write & execute test cases in ‘Formal Testing’, but no writing test cases in ‘Informal Testing’, just executing some tests based on the previous experience.
Note: No ‘Informal Testing in Automated Testing, it supports ‘Formal Testing only.
