When do you write Automated Test Script

When do you write automated Test script?

A TEST SCRIPT is a set of instructions (written using a scripting/programming language) that is performed on a system under test to verify that the system performs as expected. Test scripts are used in automated testing.
Sometimes, a set of instructions (written in a human language), used in manual testing,  is also called a Test Script but a better term for that would be a Test Case.

In today’s world, testing can not be efficient without automation. We need automation for avoiding repetitive work, making sure that the time from development to deployment is reduced with good quality. We need good, quality automation tests, not just automation tests. We need tests which are reliable, robust, easy to code, debug, scale and can run in parallel on distributed environment.

Typically, you can do testing at any point in the development cycle, therefore you can write test cases and test scripts at any point. If you have requirements to build from, you have the building blocks for test cases in the future. If you have code, you can write test cases while the code is being built. If you already have the code, you can write tests too. Do you have data? You can write test cases. Do you have configurations? You can write test cases.

When do you run your automation test cases

When do you run your automation test cases?

A test script in software testing is a set of instructions that will be performed on the system under test to test that the system functions as expected. In the test execution phase tester run automation test scripts.

How do you choose test case to be automated

How do you choose test case to be automate?

Test cases to be automated can be selected using the following criterion to increase the automation ROI:

• Business critical paths the features or user flows that if they fail, cause a considerable damage to the business.
• Tests that need to be run against every build/release of the application, such as smoke test, sanity test and regression test.
• Tests that need to run against multiple configurations different OS & Browser combinations.
• Tests that involve inputting large volumes of data, such as filling up very long forms.
• Tests that execute the same workflow but use different data for its inputs for each test run e.g. data-driven.
• Tests that can be used for performance testing, like stress and load tests.
• Tests during which images must be captured to prove that the application behaved as expected, or to check that a multitude of web pages looks the same on multiple browsers.
• Tests that take a long time to perform and may need to be run during breaks or overnight.