1. Scope of the project
Identify the correct testcase, divide the application into small parts or modules and analyze each part to come up with the appropriate test case.
- Identify the factors that will form the basis for determining testcase.
- Divide the application into small modules
- Analyze each module to identify test cases
2. Complexity of the application
- Determine application size based on the number of test cases.
- Determine the verification point and checkpoint of each test case. Here we have to set the definition of large / medium and small applications. How sorting, depends on the number of test cases.
If your application has 300 – 500 test cases for automation, you can consider it a small size application. If the test case is more than 1500, it can be classified as complex. This element may be different for different applications. For some projects, 1500 test cases for automation can be considered small / medium scale. So, once you’ve determined the number of test cases to be exact, scale up.
You must also consider checkpoints and verification points for your test case. A test case may have more than 1 checkpoint but will only have 1 verification point. In case you have more than 1 verification point, you should divide it into separate test cases.
3. Use supporting tools / technologies
- Identify Framework
- Based on need, analyze and identify the tools to be used.
4. Framework implementation
- Specify input and output
- Design input file (can be from a simple text file to a complex excel file)
- Design directory structure based on input parameters
- Implement report feature
- Implement tool for framework
- Implement unit test
There are many other requirements besides creating scripts in automation tests with Selenium, such as reading data from files, reporting / tracking test results, tracking logs, enabling scripts based on conditions and environment. input, etc.
Framework construction is very important. If your framework is solid, maintenance and updates become easier, especially in the Agile model.
5. Learning & Training
Learning Selenium is a little different than learning any other automation tool. Basically, it involves learning a programming language instead of just a scripting language (although the scripting language will help while building a framework as you want to write a script that will call the scripts themselves. Dynamic settings after making changes to the environment settings).
Along with learning java, you can learn other technologies like ANT / Maven, TestNG / jUnit, etc.
6. Environment setting
- Set up the code in a test environment
- Set up the code in the production environment
- Write scripts to enable automation test
- Sets how often scripts are run
- Create a text / excel file to import test data
- Create file for environment monitoring
7. Coding / scripting and review
- The framework is ready
- Determine the action your web application takes. It can be simple actions like navigation, text entry; or a complex action such as connecting to a database, processing flash or Ajax. Perform one test case at a time and identify all actions that the particular test case takes and estimate the appropriate number of hours for each test case. The sum of all hours for the entire test set will give you the exact number.
Above is my share of c7 factors affecting the estimation test of selenium automation project. Thank you for reading, I hope my article can help somewhat your problems!
Reference link: https://techblog.vn/cac-phuong-phap-estimate