-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[FIX] Fix asynchronous widget tests #2520
Conversation
* wait for results where needed * clanup after test
* wait for results/ready where needed * cleanup after test
f6e73b6
to
51f47e5
Compare
Codecov Report
@@ Coverage Diff @@
## master #2520 +/- ##
==========================================
+ Coverage 74.55% 74.62% +0.06%
==========================================
Files 320 320
Lines 56209 56225 +16
==========================================
+ Hits 41909 41959 +50
+ Misses 14300 14266 -34 |
@@ -215,31 +221,42 @@ def send_signal(self, input, value, *args, widget=None, wait=-1): | |||
else: | |||
raise ValueError("'{}' is not an input name for widget {}" | |||
.format(input, type(widget).__name__)) | |||
if widget.isBlocking(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Of the widget is blocking the code will not get past this check and therefore the "wait" parameter is not used. Was this intended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The (existing) wait is done after the inputs are set and handleNewSignals
is called. It is somewhat misplaced , but I do not want to change it.
Issue
Asynchronous tests for owmds and owtestlearners set inputs to their respective widgets when they should not (a per
OWWidget.isBlocking
).Description of changes
WidgetTest.send_signal
if the target widget is not ready to receive inputs.wait
parameter toWidgetTest.get_output
.Includes