- Keyword-Driven Testing (KDT) is a battle-tested method to speed up test automation development and cut down scaling costs in the long run.
- This article gives you the best practices that we’ve crystallized from our 20+ years of helping clients successfully build and maintain their KDT frameworks.
- To reap the full reward of KDT, you should 1) organize tests into self-contained test modules with clear test objectives, 2) separate Business-Level from Interaction-Level tests, and 3) architect a robust keyword library.
- As KDT is a widely adopted method, you can apply these best practices to many test automation tools including Robot Framework, Unified Functional Test, TestArchitect, TestComplete, Ranorex, etc.
In the past, test teams were often divided. Some teams would be focused on functionality, web and app server performance, UI/UX, and test automation; other teams would hone in on data, data security and performance. All of these components compose SMAC Stack (Social, Mobile, Analytics, and Cloud).Continue reading
It’s that time of the year again and love seems to be in the air (with lot of hearts and overpriced roses). No. Not this year will you be running to the store to get a mediocre box of chocolates. LogiGear has your back for Valentines Day 2019.Continue reading
“Testing is so boring.”
The bore of testing is a frequently mouthed complaint that come from people in testing who are not mentally stimulated by their work. They are no longer challenged at work and are now bored by testing. Meeting someone that does find challenge in the work process is rare. The problems they are faced with are multi-faceted and complex.Continue reading