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
However, this has the disadvantage, that with the current implementation of the testutils.github modules, only the first test is reported: For each test report, the bot checks the list of tasks in OP and only makes a comment if the test is not marked as done (i.e. if the tick box is empty):
Task 1.3 is parametrized to run the unittests seperately and give a nicely parsable result:
Release-Specs/01-ci/test_spec01.py
Lines 35 to 39 in 676d417
However, this has the disadvantage, that with the current implementation of the
testutils.github
modules, only the first test is reported: For each test report, the bot checks the list of tasks in OP and only makes a comment if the test is not marked as done (i.e. if the tick box is empty):Release-Specs/testutils/github.py
Lines 182 to 192 in 676d417
However, it then marks the tasks as done, when the test passed:
Release-Specs/testutils/github.py
Lines 192 to 199 in 676d417
This could lead to a misleading report, as all subsequent runs of the test (with different parameters) are not shown.
The text was updated successfully, but these errors were encountered: