You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 1, 2018. It is now read-only.
In unit testing frameworks (which admittedly bwoken is not) there are setup and tear down methods that can be implemented to run before and after each test. Is there such a mechanism in bwoken?
The scenario is this, and I'd be quite surprised that I'm the first to run up against it: I need to reset (or delete my app) before/after some tests so that he app starts in a known state. If I don't have this sort of thing, it makes trying to script tests pretty much useless since I still need manual steps to clear the simulator (put it in a known state) before the tests can be run.
Does bwoken all ready provide such a hook? If not, how are others dealing with putting the application into a known state before running tests? I don't see how you could do any sort of reliable tests without having a known starting state.
Thanks for your thoughts!
The text was updated successfully, but these errors were encountered:
We're using tuneup.js which create a test() method that encompass your test. I created a variation of that method that runs our sign in method at the beginning and sign out at the end of every test. You could do something similar.
Note that this does not require bwoken
In unit testing frameworks (which admittedly bwoken is not) there are setup and tear down methods that can be implemented to run before and after each test. Is there such a mechanism in bwoken?
The scenario is this, and I'd be quite surprised that I'm the first to run up against it: I need to reset (or delete my app) before/after some tests so that he app starts in a known state. If I don't have this sort of thing, it makes trying to script tests pretty much useless since I still need manual steps to clear the simulator (put it in a known state) before the tests can be run.
Does bwoken all ready provide such a hook? If not, how are others dealing with putting the application into a known state before running tests? I don't see how you could do any sort of reliable tests without having a known starting state.
Thanks for your thoughts!
The text was updated successfully, but these errors were encountered: