Clean up activities about test-butler HOT 7 CLOSED

@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.

from test-butler.

Yeah, I'm not sure closing activities is something that makes sense to live in Test Butler. I agree that it's a big pain point though.

At LinkedIn, we do something pretty similar to the code you posted for closing activities. We also get around this problem by using a custom test harness which only runs a single test per instrument command. Between each test execution, we force-stop the app and clear all package data, to ensure that the next test is starting from a completely clean state, even if the previous test failed or left activities running.

from test-butler.

Cool. Thanks for the info.

If it's possible, it'd be neat to see the closing activity code / custom test harness even if it doesn't live in the test-butler repo.

from test-butler.

Thank you!! This is awesome.

from test-butler.

@drewhannay can you throw a license banner on those gist files? I'd like to use them at work. 😄

from test-butler.

Done 😄

from test-butler.

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

edit: fixed link

from test-butler.