{"id":1917,"date":"2020-01-13T07:15:17","date_gmt":"2020-01-13T07:15:17","guid":{"rendered":"https:\/\/studysection.com\/blog\/?p=1917"},"modified":"2020-01-13T08:47:34","modified_gmt":"2020-01-13T08:47:34","slug":"top-automated-testing-practices-to-follow","status":"publish","type":"post","link":"https:\/\/studysection.com\/blog\/top-automated-testing-practices-to-follow\/","title":{"rendered":"Top Automated Testing Practices to follow"},"content":{"rendered":"

The benefits of automated testing are enormous and ROI increases exponentially if we follow the automated testing practices with proper planning.
\nHowever, it does not mean that we should completely depend on automated testing and ignore manual testing. Overall software testing procedures will always include both the manual and automation test cases to achieve high quality, better speed with optimum use of resources.<\/p>\n

So, let\u2019s discuss in detail some of the top automated testing practices we can follow while executing the test cases with automation tools.<\/p>\n

Automation testing<\/h2>\n

To move on to automation testing one of the first steps is to make sure that a stable and well-designed manual testing process is in place with the right test cases. We should consider implementing the automated testing in the project only when the environment, development code and manual test processes gain stability. Hence, with the help of manual testers, the test cases which are ideal for automated testing can be selected and can be put in an automated testing process. Hence it will save the time of manual test engineers which requires their attention to specific tasks, such as usability testing, exploratory testing, and ad-hoc testing.
\nNow the question arises, how to find which test cases to be used for the automation process. <\/strong><\/p>\n

Finding the ideal test cases for automated testing<\/h3>\n

All the test cases present in any project can be automated, but that does not mean that they all should be automated. We should plan with care while selecting the test cases for the automation process. Otherwise, we can lose money and time on creating test scripts for the cases which are not run often.<\/p>\n

The following test cases could be selected for automation because of their repetitive nature:<\/p>\n

    \n
  1. Regression Tests<\/strong>
    \nEvery time new code changes are introduced we need to make sure that it has not introduced any new defect in the code. For a QA Engineer manual execution of the regression test cases would be a time-consuming process. That is why the regression test cases are most likely to be chosen for automated testing. The QA test engineer can use this time for other important tasks that require manual testing.<\/li>\n
  2. Smoke Tests<\/strong>
    \nSmoke testing is performed whenever a new build is released for testing to make sure that the critical functionalities of the product are intact and working fine. That\u2019s why it is also called the \u2018Build Verification\u2019 testing. This testing verifies that the build is stable. As smoke tests are run after each build, so they qualify for the automated testing process.<\/li>\n
  3. Data-Driven Tests<\/strong>
    \nData-driven testing involves running data stored in several file formats like CSV, Excel, DB tables, JSON files through the same code multiple times.<\/p>\n