With the continuous development of the software industry and the adoption of Agile development cycle, Test Automation has become a hot topic in the world of software testing and quality management. But, how to automate testing for a software product, not everyone can apply it effectively. These are just the steps that I have learned through the process of learning and working with test automation. Hope it will be of some help to you on this test automation path…
Step 1: Analyze test automation applicability.
Obviously we cannot automate everything in software testing. There are new software or software writing technologies that current automation tools do not support or only partially support. The most obvious example is when we test a Web page on a new browser, and at that time, the test automation tool does not have a new version supported on that browser. Or, another example of SAP program, SAP developers have given an option to prevent auto scripting on it, and to be able to auto test on SAP we need to ask developers SAP program developers remove this option.
Step 2: Choose the right automation tool.
After determining whether the current product can perform Automation, the next step is to determine which automation tool to use. What tools support automation testing for the technology the product uses? What are the pros and cons of each tool? What scripting language does the test engine use? Are current employees familiar with this tool?
Step 3: Build a working environment.
Work environments include the concepts, cycles, processes, and environments in which test automation scripts are designed and written. Besides, it should also include the directory structure, store the test scenarios as well as the logical relationship between the components.
Step 4: Write test script, execute and analyze the results.
Based on test scenarios that have been created with manual testing, based on a scripting language supported by test automation, we write code that interacts with the software product on other environments together. and execute it. After executing the code, we need to analyze the results achieved and document the product issues, if any.
