We’re still answering questions from our April webinar on test automation! For our last question regarding Test Automation Frameworks — “What are do’s or don’ts one should know before working on a test automation frameworks” — we went to some of our test automation engineers and they had these comments:
Develop a thorough understanding of the software to be tested.
- Type of project C/S, B/S, mobile, etc – The type of app heavily influences what architecture and tools you use.
- Business logic of the software. Without knowing how to test the software manually and the logic behind it, it’s difficult to set up test automation.
- What are your automation goals? Smoke, regression?
- Understand the manual test cases and discern what is suited for automation and what is not.
- Understand the structure and format of the data so the framework can handle it today and in the future.
Understand the different types of automation frameworks so you can determine what fits your needs best.
- Modular framework (test script modularity).
- Library framework (test library architecture).
- Keyword Driven Testing Framework (keyword-driven).
- Data driven testing framework (data-driven testing).
Think about expansion and extensibility
- Understand the test requirements, and how the test automation framework will fit into the overall objectives: UI Testing, Performance Testing, Function Testing.
- Consider function expansion according to different types of projects that the framework may need to support.
- As part of the automation framework, consider how to build and deploy the test environment.
- Consider what types of various input and output will be required.
Of course, this is a short list. We could write a thesis when it comes to test automation frameworks, and we haven’t really given any Don’ts, but you get the idea.