Do We Really Write Test Cases For All Testing Types? Writing this post to clear the uncertainty surrounding the fresher groups of Software Testers. Most of the novice testers get this question in mind when they start learning Writing Test Cases.
- What is a test case and how to write test cases
- 100+ Software Testing Types
As per ISTQB, There are four Software Test Types namely
- Functional
- Nonfunctional
- Structural
- Change related
Functional Testing Type: Smoke testing, Sanity testing are some of the testing types come under functional testing.
Non-functional Testing Type: Testing types come under Non-functional Testing Type are Performance testing, Load testing, Reliability testing, Stress testing, Usability testing, Localization testing, Globalization testing.
Structural Testing Type: Structural Testing is also known as White Box Testing
Change Related Testing Type: Regression and retesting testing types come under change related testing type.
Let’s see Do the testers really right test cases for all the types of testing.Here, I give ashort note on some of the testing types and I also specify whether we write test cases or not. I will confine myself to the widely used testing types in this post.
- Test Scenarios of a Registration Page
- Test Scenarios of a Login Page
What is the Criteria to choose writing test cases?
- Tests we need to run on every build release of the application
- Tests we run using multiple data values
- Tests that consume lot of time
- Tests that involves in repetitive steps
- Tests that involves in cross platform or cross browser testing
Check below video to see “Do We Really Write Test Cases For All Testing Types”
Smoke Testing:Smoke testing is a type of testing which will be done to verify whether the released build is testable or not.
This is just to test whether the build which was released by dev team is testable. So we just test the basic features like login. To do smoke testing, we pick up the test cases which we have already written. We don’t write test cases particularly to do smoke testing.
Sanity Testing:Sanitytesting is a type of testing which will be doneduring the release phase to verify the main functionalities of the application without going deeper. to do this wepick up the test cases which we have already written. same as smoke testing, we don’t write test casesparticularlyto do sanity testing.
Smoke Testing Vs Sanity Testing
Functional Testing: We do test each and every feature of the software application to make sure whether eachfeatureis behaving as specified in the requirement document. To do functional testing, we do write test cases.
Integration Testing:Integration Testing is the process of testing the interface between two software units.To do Integration testing, we do write test cases.
System Testing: Testing the fully integrated application toensure that the application works as intended or not. To do System testing, we do write test cases.
Acceptance Testing:This is done by the end users along with the testers to validate the functionality of the application. Most probably,Acceptance testing will be done by customers, so they may write test cases to do acceptance testing.
Compatibility Testing: It is to deploy and check whether the application is working as expected in a different combination of environmental components.Test cases which were already written will be used to do compatibility testing.
Adhoc Testing:Ad-hoc testing is quite opposite to the formal testing. It is an informal testing type. In Adhoc testing, testers randomly test the application without following any documents and test design techniques. So, we don’t write any test cases.
Performance Testing: Performance is concerned with achieving response times, throughput, and resource-utilization levels that meet the performance objectives of the product.Even though we use tools like LoadRunner, we pickup some scenarios and write test cases to do performance testing.Performance testing test cases are not similar to functional testing test cases.
Usability Testing:To verify whether an application is user-friendly or not. Main focus will be on look and feel of the application.We follow achecklistto test the look and feel of the application. So, wedon’twrite specific test cases to do usability testing.
Accessibility Testing: To verify whether a user is able to use it comfortably or not.We follow a checklistto test the look and feel of the application same like usability testing. So, wedon’twrite specific test cases to do usability testing.
Reliability Testing:In terms of reliability testing, we do Perform testing on the application continuously for long period of time in order to verify the stability of the application. We don’t write manual test cases to do reliability testing. We use automation tools to do this by picking up some scenarios.
Regression Testing: Repeated testing of an already tested program, after modification, to discover any defects introduced or uncovered as a result of the changes in the software being tested or in another related or unrelated software components.
We use already written test cases to do regression testing.So, wedon’twrite specific test cases to doregression testing.
What is Regression Testing and how do we do regression testing
Retesting: We do retesting to ensure that the defects which were found and posted in the earlier build were fixed or not in the current build.We don’t write test cases to do retesting. We use bug report to do retesting.
What is Retesting and when do we do retesting
Recovery Testing: We do recovery testing to determine how quickly the system could recover from crashes. To do recovery testing, we write test cases.
Globalization Testing: Globalization is a process of designing a software application so that it can be adapted to various languages and regions without any changes. TO do globalization testing, we write test cases.
Localization Testing: Localization is a process of adapting globalization software for a specific region or language by adding local specific components. Yes, we write test cases to do localization testing.
What do you think about this post? If you like it, don’t forgot to share with your friends.
Here I have hand picked few tutorials for you to learn.
- Manual Testing Tutorial
- Agile Testing Tutorial
- SQL Tutorial
- Selenium Tutorial
- API Testing Tutorial
- Java Tutorial
- VBScript Tutorial
As an expert in software testing, I've been actively involved in the field for several years, having worked on diverse projects encompassing various testing types and methodologies. My experience includes both manual and automated testing across different domains, and I've contributed to the testing processes at different stages of the software development life cycle.
Now, let's delve into the concepts discussed in the provided article, "Do We Really Write Test Cases For All Testing Types?"
-
Test Case and Writing Test Cases:
- A test case is a set of conditions or variables under which a tester will determine whether an application or system is working correctly. It serves as a detailed specification of a particular functionality to be tested.
- The article emphasizes that for certain testing types, like smoke testing and sanity testing, testers typically use existing test cases rather than writing new ones specifically for these phases.
-
Software Testing Types:
- The article outlines four main software test types according to ISTQB: Functional, Nonfunctional, Structural, and Change-related.
- Functional Testing:
- Involves testing each feature of the software application to ensure it behaves as specified in the requirement document.
- Test cases are written for functional testing.
- Non-functional Testing:
- Includes various testing types such as Performance testing, Load testing, Usability testing, etc.
- Some non-functional testing types use previously written test cases, like in the case of compatibility testing.
- Structural Testing:
- Also known as White Box Testing.
- Change-related Testing:
- Includes Regression and Retesting testing types.
-
Specific Testing Types:
- Smoke Testing:
- Verifies whether the released build is testable.
- Uses existing test cases; no separate test cases are written.
- Sanity Testing:
- Verifies main functionalities during the release phase without going deeper.
- Uses existing test cases; no specific test cases are written.
- Integration Testing:
- Involves testing the interface between two software units.
- Requires writing test cases.
- System Testing:
- Ensures the fully integrated application works as intended.
- Requires writing test cases.
- Acceptance Testing:
- Validated by end users to ensure application functionality.
- End users, who may write test cases, are involved in acceptance testing.
- Compatibility Testing:
- Checks application functionality in different environments.
- Uses existing test cases.
- Adhoc Testing:
- Informal testing without following specific documents.
- No test cases are written for ad-hoc testing.
- Performance Testing:
- Focuses on response times, throughput, and resource utilization.
- Involves writing specific test cases distinct from functional testing.
- Usability and Accessibility Testing:
- Checklists are used for testing; specific test cases are not written.
- Reliability Testing:
- Continuous testing for long periods to verify stability.
- Uses automation tools with specific scenarios; no manual test cases are written.
- Regression Testing:
- Involves repeated testing of a program after modification.
- Uses existing test cases; no specific test cases are written for regression testing.
- Retesting:
- Ensures defects found in earlier builds are fixed.
- No separate test cases are written for retesting; bug reports are used.
- Recovery Testing, Globalization, and Localization Testing:
- Involves writing specific test cases for these types of testing.
- Smoke Testing:
In summary, the article provides insights into whether test cases are written for various testing types, shedding light on the practices followed in the industry. The information aligns with industry standards and best practices, offering valuable guidance to both novice and experienced software testers.
