Automation tool selection can be a big problem,<\/p>\n
Here are a few fundamentals I try to stick to:<\/p>\n
1. Goals of the project
\n– Be crystal clear on what you want to accomplish with the project
\n– While most automation projects might have similar end goals, not all would have the same priority<\/p>\n
2. AUT
\n– The most important factor to dictate this decision, understand the AUT (Application under test) and figure out what you should value the most in your automation framework.<\/p>\n
3. Integration
\n– Your automation framework might not (or should not) comprise of any one tool,
\n– Make sure it integrates well across the SDLC especially any CI tool (even if you have no plans for CI)<\/p>\n
4. Support
\n– Automation tools have to put with a LOT of change,
\n– Make sure the community surrounding the tool \/ library is very active and on top of their game,<\/p>\n
A few more points and further elaboration on the ones discussed here in linked article<\/p>\n
#QsDaily #automation #automationtool #automationframeworkdesign<\/p>\n<\/div>
http:\/\/quality-spectrum.com\/automation-tool-selection-dilemma\/<\/p>\n<\/div>