
Why You Need at Least Three Sets of Eyes on Your Code
Whether your team prefers pair programming or mobbing, “three sets of eyes” is a good starter rule for achieving quality code.

Whether your team prefers pair programming or mobbing, “three sets of eyes” is a good starter rule for achieving quality code.

As the pandemic goes on, a majority of the workforce is still working remotely. If collaboration at a distance is a struggle, it’s time to fix it. Here are some ideas and tools to improve communication on remote testing teams.

Check out why taking the time to resolve your failed test cases, and to learn from the failures, will help make your entire test suite more reliable.

Got test maintenance headaches? Learn how using an object repository helps you build more maintainable software tests.

Teams build robust automation suites in hopes of finding bugs faster and decreasing manual testing effort. But how do you know this pursuit is successful?

E2E testing, despite its challenges, is important to validate the workflow of an application from the end user’s perspective. Let’s look at the pros, cons, and how to get started with E2E test automation.

The only thing worse than leaving a hole on the team is filling it with the wrong person. When it comes to testers, we’ve identified nine things to look for—and how to identify them in a candidate.

Increase productivity and reduce hand-typed, potentially brittle test code with scripts, snippets, and functions.

Multitasking doesn’t make us more productive. Try a “one thing at a time” approach to reduce productivity loss, delivery time, and cost.
