-
Notifications
You must be signed in to change notification settings - Fork 574
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.
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
More thorough testing mode #1215
Comments
Agreed. As I wrote before, I'm in process of transforming that 30 sec timeout into 30 sec since last API command (after synchronization finish - with your elaboration). Basic testing I've planned to implement trough API commands (address creation, message sending). That's why I'm doing cleanup of the |
I think there should be a separate API test. |
With API at least I understand how to implement such tests. You can check the first results in my branch test-mode. Otherwise the tests should apparently be asynchronous and will probably require sophisticated testing lib... |
You can run the tests in the main thread (which normally runs the GUI and in the daemon mode does nothing). As for getting feedback, you just do a non-blocking get on the relevant queues (e.g. the ui signaller queue and address generator return queue) with a small timeout. It shouldn't be very difficult. |
Instead of just sleeping for 30 seconds before shutdown, the testing mode should:
The text was updated successfully, but these errors were encountered: