The following table provides you a script generation check list:
| Sl. No | Task list | Status |
| 1 | Does your utility files and code files limit is within 2000 lines of code, if not, are you creating a separate file? |  |
| 2 | Does the script follow coding guidelines using tools, such as Pylint? |  |
| 3 | Is the script free from unnecessary delays, such as Hardcoded delays ? |  |
| 4 | Are you avoiding the duplicate code in your scripts? |  |
| 5 | Does the script handle application errors as designed? |  |
| 6 | Are you enabling soft assertions in scripts? |  |
| 7 | Have you added comments for all methods in the script to explain their purpose, inputs, outputs, and important details? |  |
8 | Are you modifying the scripts that are generated? |  |
| 9 | Are you generating comprehensive test reports that document test execution results and findings? Reports must include details on test coverage, pass/fail status, any issues identified, verification steps, and corresponding screenshots. |  |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article