Quote:The DataSheet is over a thousand lines long and gong through it gives me a headache.
Are these thousands of lines of keywords? If yes, then its a bad design to begin with. Keyword driven frameworks are generally quite easy to make, thus, automation developers should pay more attention to usability because keywords are generally created by users, not the automation developers. If you, being an automation developer yourself are having a tough time dealing with the way the code has been written, then I doubt the methodology is to be blamed. Its the design. Creating more functions does not make a framework more usable.
Have you had a chance to try any other keyword-driven frameworks? If not, you can give the below 2 a try:
FrameworkManager
Demo Framework: RelevantCodes[1]One
Quote:And this one .vbs file has several hundred functions for each functionality in the Application.
Sounds like an overkill to me, but because I haven't seen the library, its definitely a bold thing for me to say. To be able to understand everything though is a very common issue both on the Test Automation as well as the development side. Even with good documentation, it can become hard to follow the logic used by another person. If a test-suite contains tons of functions doesn't mean its necessary doing more work
