T&A: 43407: Fix missing StatusOfAttempt #8823
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lukas-heinrich
force-pushed
the
bugfix/10/43407
branch
from
7a21b0d to
7b39caa
Compare
lukas-heinrich
force-pushed
the
bugfix/10/43407
branch
from
7b39caa to
64d6a39
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi everyone,
this PR refers to the ticket 43407, which describes an incorrect display of the Status Of Attempts.
The behavior described can be traced back to the fact that the object's properties are not set at any point, which I have added. Setting
StatusOfAttempt::RUNNINGat this point may look irritating. When debugging, however, I was able to determine that thegetAttemptOverviewInformation()method is not executed if there is no pass. Accordingly, it can be assumed that the status at this point is at least Running or that the test run has already been completed.I look forward to your feedback and am open to suggestions or questions. This PR was co-authored and internally reviewed by @thojou.
Best,
@lukas-heinrich