• Automation testing requires investment in time, efforts and resources. This investment should be planned smartly. Below factors need to analyzed before considering automation for test suites:

    - Smoke/Sanity test cases should be automated on top priority as these are the most important use case scenarios with respect to the core business flow.

    - For every minor/major releases all the suites - Sanity, Smoke and Regression suites should be executed. 

    - Test should be executed taking care of browser/platform matrix defined by client end. 

    - In case of data driven frameworks, different multiple sets of data should be used so that test coverage can be increased. 

    - Using contiuous testing tools like Jenkins, CircleCI or TravisCI, automatic jobs for running suites should be triggered so that test results are in the email box at the earliest. 

    - Failed test cases screenshots should be available for analysis of automated test results. 

    This criteria is usually followed by leading software testing company for analyzing the feasibility of automation. 

    The Best Software Testing Services Company - QASource
    Partner with the leading software testing company, QASource, and accomplish all your software testing goals within strict deadlines and budget. We pr…
This reply was deleted.
    results->result as $result) { ?>
  1. jobtitle;?>
    company;?>(formattedRelativeTime;?>)city;?>, state;?>
    Welcome to Mobile QA Zone, a Next Generation Software Testing Community.Invite your friends to join this community.Write to us to become a featured member.