In this Maintenance Testing guide, we will discuss everything you need to know about Maintenance Testing.
What Is Maintenance Testing?
In software testing, there are more than 100 types of testing and this maintenance testing is one of them. As a tester, we do testing software during its pre-release stage. We also perform testing on the software after it is released. Performing testing after it is released is known as maintenance testing.
Why Maintenance Testing Is Required?
In general, the software runs many years after it is released.
At times we need to correct or upgrade the software during its run time.
Planned enhancements by the Software Development Firms such as corrective and emergency changes, changes of the operational environment, and patches for defects and vulnerabilities
Request from the end-users to add new features to the existing software.
End-users may want to migrate from one platform to another such as upgrading their environment like operating system, database, etc.,
With the latest updates in the technology if we don’t upgrade the software then it will become obsolete.
It becomes a compulsion on the Software Development Firms to upgrade the software regularly to keep the software up-to-date.
These modifications need to be tested thoroughly. The testing type that is done during this upgrading or enhancing or migration phase is known as Maintenance Testing.
Types Of Maintenance Testing
While performing maintenance testing, testers should consider two types of maintenance testing.
- Confirmation Testing: Testing the modified functionality
- Regression Testing: Testing the existing functionality
#1. Confirmation Maintenance Testing:
It is to test the modified functionality.
During this part of maintenance testing as a tester, you have to test all the modifications (either small or big) made in the software thoroughly and make sure that there are no functionality issues and downtime.
Note: The test environment should be a replica of the live environment along with test data.
#2. Regression Maintenance Testing:
It is done after the confirmation maintenance testing phase. It is to test the existing functionality
As a tester, you have to test the complete system to make sure the modified functionality (maintenance work) shouldn’t affect the functionality of the existing software is known as Regression Testing.
Let’s summarize what we have discussed so far.
- Performing testing after the software is released is known as maintenance testing.
- Maintenance testing is different from new application testing.
- There are two important parts of maintenance testing such as confirmation maintenance testing and regression maintenance testing.
- What is Software Development Life Cycle (SDLC), Phases, SDLC vs STLC
- What is Confirmation testing in Software?
- Best Regression Testing Tools
- What is Regression Testing and when do we do regression testing
- What is Retesting and when do we do retesting
- What is Defect, Bug, Error, and Failure in Software Testing
- Unit Testing Guide
- Integration Testing Guide
- System Testing
- Acceptance Testing
- Functional Testing Guide
- Non-functional Testing Guide