Sometime you need to test how your code handles an uploaded file, but you don’t want to upload it in your test. Luckily, there’s an easy way to handle this.
Figuring out why your feature tests are failing can be difficult, especially when setting up the first few tests in the codebase.
You don’t need an
sleep() is fickle. Make Espresso wait for your observables running on background schedulers with this one cool trick!
When we stub an intent, we are able to intercept it so the intent is never sent to the system, and specify how it should respond. This can be helpful in your Android tests when you need to know if an intent was sent, but you don’t actually need the Activity to start. This can be accomplished by using espresso-intents.
Using espresso-intents for testing Android Activity Intents
Some tricks to help you fix tests that sometimes fail.
Check your at_exit callbacks.
Recently one of our projects called for using the browser’s Geolocation API. We were excited about this project. However, we had an immediate concern about how to test a feature that interacts with one of the browser’s built in APIs.
When strange failures are plaguing Firefox during Travis CI test runs, get a hold of Travis Support, they’ll help you out!
I joined Collective Idea six months ago. In that time, I’ve had the chance to throw myself into a new language. Just like learning a new spoken language, learning a new programming language means learning a new way of thinking. Here are some of my reflections on becoming a Rubyist.
“I don’t have time to test” seems to be somewhat of a recurring theme in hurried projects. Stop lying to yourself—and your clients.