If there are no automated tools for regression testing the main attention focus on manual testing, aimed to re-affirm the ‘known’ state of software after modifications. This may tie up a great quantity of high-priced resources or simply avert changes from being delivered successfully at short notice.
In these conditions pressures can lead to the shipping of software which has not been enough re-tested after modifications. It also can be dreadful after-effects.
To keep competitive ability, software developers must be able to implement changes to software rapidly and dependable.
To support quick change, testing must consequently be both complete and rapid, leaving little option but to automate the testing process.