Tools
Articles
![]() |
The Rise and Fall of Protractor, and Why You Should Stop Using It Protractor has been a popular choice for writing end-to-end (E2E) browser tests over the past decade. However, Protractor is being removed from the Angular project as of Angular 15 due to a loss of dedicated developers and the rise of better testing frameworks. Based on this state of affairs, what should developers working with Protractor do, and what tool choices do developers have going forward? |
|
![]() |
Just a Tester? A Report Part-Way Through Data Analysis Testers come from a wider range of backgrounds, and have complex multifaceted roles. People who test are not “just testers…” At present, many testers do not feel well-supported by their tools. As my research uncovered stories of frustration, fear, and anger, I realized the illusory role of usability in tool adoption and the importance of understanding who is using those tools. |
|
![]() |
Cucumber for BDD—How Effective Is It? Whether to use Cucumber and BDD (Behavior Driven Development) is an old topic and a lot has been shared regarding this already. However I believe many times it’s just the high level technical reasons that make it to the forefront of the argument on how effective it is, and I want to address the topic from a holistic point of view and not just technical. |
|
![]() |
False Errors in Test Tooling Traditional GUI automation is linear; it follows a set of steps. The first time you run it, it can't add any value, as the feature isn't done until the automation runs. Once test automation runs a second time, it effectively becomes change detection. This leads to a large number of "failures" that are not actually failures. Whether they are false positives or false negatives, we need a way to fix the automation tooling. |