Tools are a normal part of testing jobs because they can amplify our ability to learn about product quality. It's a good idea to review new tools for automation, performance, or monitoring to see if some solution will help you test better. Before you even look at tools, though, there are two questions you should ask.

Pull requests may not seem to fit into agile development, but they can work well if done right. If you can maintain feedback on your working software from frequent integration, using PRs can help people understand your code. The speed at which PRs can be reviewed depends on three things: context, size, and atomicity.

Test design can contribute greatly to how manageable and maintainable your automation is. Hiding detailed steps in actions makes their automation easier to maintain, and the high-level actions can be leveraged to define less common tests. Here's how you can write tests as a sequence of actions to improve coverage.