We all know that Automation projects are different from Manual test projects. Although automation projects do not really exist (or do not exist as an ideal), both automation and manual projects are handled differently within the plan step. A project whose plan is unclear cannot be implemented properly; This not only affects current projects and adversely affects individual ability, but it can also lead to loss of customer confidence, management, and business impact. .
Before going to the next section, I want to note that this article does not go into the following.
- There is no discussion here about automation frameworks. Different projects use different frameworks depending on the nature of AUTs, architecture, complexity and expertise of the team.
- The article does not discuss template, format or how to create a test plan document. We will address the issues that need to be considered when creating the documents before starting an automation project, analyzing the feasibility before making the project.
- This also does not mention a specific tool
For a manual testing project, the cost factors are:
- Tools – Test / manage defect
- Infrastructure – environment, infrastructure
For an automation project, in addition to the above items, it needs costs for:
- Automation tools
- Add-in to manage test tool
- Add-in to support the application being tested (Application Under Test-AUT: eg SAP, oracle etc)
- Setting up the Framework
Training uses a few special test tools
In that situation, the success of an automation project depends on how to write code, how much of the written code can be reused or with how many lines of code can achieve the desired result? If the answer to this question is "NO" then you have planned for automation projects incorrectly.
Usually, a plan test has the following sections.
The sections in Test plan of Automation test
# 1: Scope (Scope)
- Selecting Test cases / scripts can be reused many times when the test turns around
- Sometimes the simplest test case also needs a lot of complicated solutions to test automatically. If this test case is used only once, then obviously there is no meaning. Also because it can be reused many times, it is necessary to concentrate and put effort into it.
- Automation test cannot execute exploratory testing
# 2: Test strategy (Test strategy)
- This section is considered as a framework in automation test. Some frameworks are very difficult to create and also effective but require time, effort and capacity. Try to find the best solution that can be done without harming the use of resources.
- Decide on the best way to write code for automation test, naming convention, location to store test and format devices of test results, … to maintain uniformity and increase productivity.
# 3: Resources / roles and responsibilities (Resources / roles and responsibilities)
- The first step is to understand the capabilities of the group and anticipate the scope of automation in the overall. This will help select a team that matches the needs of both automation and manual testing. Also, choose the right people – those who don't think manual testing is below their reach.
- Choose a team proficient with AUT, test management, defect management and other SDLC activities
# 4: Tools (Tools)
Choose automation tool based on the following rules:
- If the tool test is not free, the company already has a license for that tool
- You can find open source tools but need to select
- The members of the group know about this tool or have not used it, otherwise they need to bring new people into the team or not training for old people.
# 5: Schedule (Schedules)
- Include time for code and check automation scripts (automation scripts)
- Maintain scripts on a regular and timely basis. If you create a code that you will not use for the next 6 months or longer, you need maintenance to reduce the possibility of failure.
# 6: Environment (Environment)
- The environments that AUT will run and the automation tool you want to use must be compatible. This is one of the factors considered when choosing a tool.
# 7: Distribution (Deliverables)
- You create test scripts, however, not everyone understands about automation / programming languages. So there should be a plan to create a "Guide" document to help current and future users to understand this scenario even without you.
- Include comments in the script.
# 8: Risks (Risks)
- If you will propose an automation solution, be sure to choose the right and cost effective tool to ensure that automation implementation does not become a burden for the project. It is important to determine that the benefits gained by investment automation are not immediately visible but can be seen in the long run. So if you propose system automation, select the tool with the same properties
- Maintain stability and do not need too much maintenance
- There is scope for large regression ranges
- No need to intervene too much by hand, regardless of human intuition
# 9: test data (Test data)
- Take into consideration the security aspects of data
- Do not directly put test data into the script. This may cause an error during the modification or maintenance process.
- Test data should be very specific. For manual test step – 'enter name', it is possible to enter any name of 5 characters. During the test, you can type "Swati" or "Seela" or any other name. But for automation test that cannot make such assumptions, it is necessary to enter the correct value
# 10: Report / result (Reports / results)
- The results of Script execution are also technical and maybe not everyone in the team understands. Plan should write down the details of the results done in the document file or excel file as an additional measure
- Framework documents, review results, defect reports, status .. needed in the report
Sometimes it is not easy to propose customers / managers to buy automation tools. However, when the ultimate goal of automation test is to maximize profits, it is entirely consistent with the objectives of the manager / customer. This will ensure that not only can we implement automation in the project but it also receives the consensus, cooperation and excitement of many stakeholders.
A careful planning and analysis of all the factors listed above can help us see the many benefits of automation test and the necessary factors when looking for a tool test.