Clean up activities

One issue I’ve run into using test-butler with Espresso testing, is that activities don’t get cleaned up. I’ve had to adopt code like this to make sure activity.finish(); gets called after tests run.

• Is cleaning up activities beyond the scope of test butler?
• How does linkedin deal with retrying failed tests if there’s no way to close the activities from a failed run?

[drewhannay]

@bootstraponline Here’s a gist of what we use for closing activities

The custom test harness is harder to show off, since it’s a lot of code. It’s fairly similar to Shazam’s Fork runner. I’d love to open source it someday, but right now it has too many dependencies on internal things and we haven’t had the time / resources to refactor and extract the right parts.

[bootstraponline]

Thanks! It’s working really well with our internal tests. The changes will be in the next open source sync.

edit: fixed link