Learn how to recognize and mitigate dependencies so that you can test your own software without relying on integration and E2E environments.
Dependencies are present in every project; some code over here needs code over there, and we can't be sure the code over here works until the code over there is done! Well, sure, that makes a kind of sense. But often teams take this to an extreme; they allow themselves to become blocked, or even worse, hinder other teams from making progress due to their demands. We'll learn how the types of dependencies (defined here as Blockers, Yaks, and Mirrors) can be recognized, and overcome and especially how true blockers can be avoided with good understanding of the system architecture and a grasp of test automation techniques.