Now a days, Why Automation Testing is required?

Automated software testing is the good way to generate the effectiveness, efficiency and coverage of your software testing project. Every software development group tests their products/application, Delivered software always has some defects.

Software Test engineers job is to catch them before the product/application is released but they always creep in and they often re-appear, even the best manual testing technique.

An automation software testing tool is meant for playback pre-recorded and predefined actions compare the results to the expected behavior and report the success or failure of these manual tests to a software test engineer.

Once automated tests are designed or created it can easily be repeated and it can be extended to perform tasks which is impossible in manual testing. Because of this, qa/project managers have found that automated software testing is an essential component of successful development projects.

Manual software testing is that manual tester are sitting in front of a computer and carefully going through application screens, trying with various usage and input combinations, comparing the results to the expected behavior and recording their observations and issues if any identified.

Manual tests are repeated always during the development cycles for source code changes, now the other situations is like to manually check the multiple operating environments and hardware configurations.

Automation testing importance during software testing process.

Companies are not only want to test software /application adequately, but also as quickly/thoroughly as possible. Accomplish this type of goal, organizations are go for an automated testing to increase the test coverage. Reducing the need for manual testing and discovers defects manual testing cannot expose and also manual testing is error prone and a very time consuming process.

Running the test case again gives us the confidence that the new feature development. System did not break the code that used to work and also to make sure that the new feature changes we introduced are working fine.

Executing the tests (mostly acceptance (UAT) tests) can also help to understand what portion of the desired functionality has been implemented.