1. Plan the Road map

• Review App road map: On the first phase of automation, our QA review the app and go through the app documentation to take clear idea about application functionalities.
• Review manual test cases: Once application functionalities are cleared by our QA then they'll review the manual test cases of application.
• Verify testability: Our team will check the manual test cases and pick the cases to automate from those manual cases.
• Selection of automation candidates: Once the application review is completed we choose the best automation engineer as per application requirement from our team for automating tests.
• Define test strategy: Once the automation team is ready we define the test strategy for automation testing of application.

2. Design the Framework

• Re-factor manual tests to be ready for test automation: At this stage our automation team verify the manual cases and filter the cases as per the priorities of automation.
• Framework design: At this stage we change our custom framework to the application specific framework as per the application requirement.
• Plan reusable libraries: Reusable library contains component of code that we design to write the more optimized code and reduce the redundancy.
• Data management plan: In this stage we modify the framework and add few features or functionalities required for application. (I.e. Create Test data etc...)

3. Develop the automation test scripts

• Create Test script: This is stage when we start to automate the manual tests into test scripts. Test scripts are created by our QA team as per it's defined priorities and designs.
• Data Management: While executing the test scenarios, our team prepares & execute the test data using the requirements of the logical test scenarios.
• Build execution flow: We will configure build with Continues Integration Server like Jenkins it will manage the Automation Test Build Execution. This will be used to run the automated test suite everyday using pre-scheduled tasks or on need basis. This will fulfill the need of a vital regression test suite.
• Recovery scenarios: We will setup Retry Analyzer Listener which is part of TestNG Framework to enhance the stability.
• Add to function libraries: This contains Logic and verification methods required to execute the logical test case functionality.
• Tools extension: Selenium Webdriver, Appium, Maven, TestNG are the tools used in this automation testing. Jenkins is used for CI integration.
• Repository management: On the daily basis our QA team also push the code in repositories as well like Git, svn etc... this will ensure that all changes in code are secure and everyone has access to latest code.
• Documentation: We will deliver user guide to setup Automation Test Environment with Continues Integration.

4. Script execution on environment

• Create new test environment: For the test execution, Test environment also created online in virtual machine or in local client machine.
• Deploy test suite: In the test environment our team deploy the test suite to execute on that environment.
• Execute test scripts: After successful test script development and deployment our engineer executes that in the test environment. Custom additional verification and assertion steps can be added in this stage (on client request).
• Result Reporting: At this stage after every execution test report is generated for the result of execution. This report gives brief idea of app execution which mail to the all the stack holders of project. When using a Jenkins build this mechanism is also channelized via Jenkins reporting.
• Defect Management: After execution, test reports will give brief explanation of failure and defects faced during automation execution. A bug is logged in client’s used bug reporting tool.

5. Test script maintenance

• Update Assets: As per changing functionalities or build our team keep updating the test scripts, test framework dependencies, libraries, browsers versions, environment, Java versions etc. for successful execution of the automated test suite.
• Maintain test suite: Test suite will require maintenance and upgrades. whenever changes are introduced in the following:
  • Software requirements changed or modified.
  • Modifications in GUI front end.
  • Changes in back end logic etc.
  • Functionality made obsolete.
  • Buttons renamed, removed etc.
• Regression Test: Our team keep doing regression testing every time new build is received to check the application functionalities. Regression tests can be performed on demand basis or by scheduling an automated Jenkins job. If required, the same test suite can be run on older software versions to check and monitor software behavior in different software releases.