There are so many writers, bloggers, and influential people in the software testing industry who are just so amazing at what they do. This is a post dedicated to giving them the limelight they deserve and to shine some attention to their most recent articles and posts.Continue reading
A tester’s job is to find bugs. It’s critical that they find the important technical bugs and customer focused bugs. It’s even more critical that they find them as early as possible because they will be much cheaper to fix. However, in order to achieve this, testers have to do a great job testing.Continue reading
- 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 Keyword-Driven Testing frameworks.
- To reap the full reward of Keyword-Driven Testing, 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 Keyword-Driven Testing 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