Skip to content
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 Attribute Errors #980

Merged
merged 4 commits into from
Aug 15, 2023

Conversation

M6AI
Copy link
Contributor

@M6AI M6AI commented Aug 9, 2023

Bug / Requirement Description

There are two attribute errors related to the interactive UI with filter expression feature. One is a silent exception thrown on rerun of single testcases on a missing length attribute. The other is related to running a single testcase where the filtered runtime status was not implemented.

Solution description

Added proper handling for these scenarios and an additional test for running a single testcase with an API call.

Checklist:

  • Test
  • Example (both test_plan.py and .rst)
  • Documentation (API)
  • News fragment present for release notes
  • MS info leakage check
  • For new driver: driver index page
  • For new assertion: ui/pdf/std renderers, documentation
  • For new cmdline arg: documentation

…tal attribute error thrown by the backend on filtered runtime status.
@@ -0,0 +1 @@
Fixed silent exception thrown by the UI when attempting a rerun of a single testcase with an active filter.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merge the 2 news fragment? they read very similar to me.

entries[child["name"]] = {}
# NOTE: we ignore assertions (DEFAULT category) and testcases
for child in entry.get("entries", []):
if child["category"] in ("DEFAULT"):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we shall rely on the category of child. Can we check the category of the entry upfront, as the stop condition for this recursive function?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me check I remember, having some weird scenario, but perhaps with the update to frontend that is gone as well.

@M6AI M6AI merged commit 0a875ed into morganstanley:main Aug 15, 2023
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants