Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Kill AsyncTasks during finishOpenedActivities? #395

Closed
renas opened this issue Aug 19, 2015 · 2 comments
Closed

Kill AsyncTasks during finishOpenedActivities? #395

renas opened this issue Aug 19, 2015 · 2 comments
Labels
bug imported Priority-Medium wontfix

Comments

@renas
Copy link
Contributor

renas commented Aug 19, 2015

From glenview...@gmail.com on August 23, 2012 05:39:18

During many of my tests, my app is running AsyncTasks that access the database and cannot be cancelled. At the end of my tests, I close my database, delete it, then reopen it so I have a fresh database fixture.

The problem is that when the AsyncTasks happen to still be running during the time when the test is closing and deleting the database, I'll get a runtime exception in the code. This couldn't ever happen in the production code because the database is never closed in production.

If there were some way for you to modify the finishOpenedActivities to ensure that all child threads (AsyncTasks specifically) were finished as well, that would be tremendously helpful. Otherwise I probably have to go implement checks for cancelled in all my AsyncTasks just to support reliable testing. I don't even know if this is possible with the Android API though.

Thanks!
Jeff

Original issue: http://code.google.com/p/robotium/issues/detail?id=316
@renas
Copy link
Contributor Author

renas commented Aug 19, 2015

From renasr...@gmail.com on August 26, 2012 22:59:13

I think its best if you wait for your async tasks to complete before you use finishOpenedActivities().

Status: WontFix
Owner: renasr...@gmail.com

@renas
Copy link
Contributor Author

renas commented Aug 19, 2015

From glenview...@gmail.com on August 27, 2012 07:16:35

I'd love to.. hence the enhancement request. Most of my async tasks produce no visible artifacts because they are doing background initialization. I could sleep for several seconds at teardown tests but that would slow things down quite a bit.

@renas renas closed this as completed Aug 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug imported Priority-Medium wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@renas