With API testing, if you change how the API works—even if it now works better—it will break all of the code written by people using the API. Consequently, testers have a responsibility to make sure they are testing the same contract that was established when the API was first released. Here's how to test APIs right.

Sprint retrospectives are often skipped, compressed, or organized in a way that doesn't provide good feedback. This is unfortunate, as a well-planned retrospective is a great way to improve how you work. Good retrospectives enable engagement and safety, distill and prioritize ideas, and create concrete action items.

When testing applications, documenting and interpreting test results can be a challenge. Data models enable us to collect and process test data more dynamically and uniformly. To design effective data models for self-documented tests, there are three important things to consider: what to document, collect, and report.