Testing in the Open
“Automation is not testing”
I recently attended a webinar where the speaker made this comment and it started me thinking about testing in general and what some of the challenges that can present.
We all know that we should be testing, but there are a lot of potential pit falls that one can fall into when starting down this journey. I’m going to jump into the deep end of the pool here and deal with one of the struggles that it took me a while to deal with.
Imagine the following:
- You have a local device with a REST API
- You write a library that accesses that REST API
- You write tests for that library so that it runs against the local devices REST API
- You push the library to GITHUB so that other people can leverage your work. ( You are a good person, right?)
- You configure TravisCI or CircleCI for integration testing.
- You realize all your tests fail because Travis/Circle doesn’t have access to your internal device.
And now your GITHUB badges all show red and no one trusts your code. Which brings us to vcrpy
What’s vcrpy?
Wow! So glad you asked! vcrpy is a REST Continue reading

