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.
If you’re a tester or programmer:
* You’ll learn how to recognize and diagnose the types of dependencies you’ll face.
* You’ll be (re)introduced to Agile Testing models and automated checking techniques (with a twist!) that will help you overcome these dependencies.
* You’ll be confident that you can test your software without having to ALSO test the software that you depend on.
* You’ll (maybe) be able to convince the people who run the software that depends on YOUR software that they don’t need to test YOUR software.
If you’re a manager or architect:
* You’ll learn about the dependency traps you’re setting by how you decide on and set up processes and tooling.
* You’ll be better equipped to recognize the dependencies you’re creating between teams and organizations that create the components that make up your solutions.
If you’re anybody involved with software development:
* You’ll approach common software dependencies that you’ve always assumed to be insurmountable in a new way.
You’ll learn how to Test Your Own Stuff!
You must be a Member to view this post and you are currently not logged in.
You can either log in below or sign up here.