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

Update Test Reports, Test Queue and Test Run pages #419

Merged
merged 63 commits into from
May 31, 2022

Conversation

howard-e
Copy link
Contributor

@howard-e howard-e commented May 3, 2022

This implements sweeping changes across the Test Reports related pages, Test Queue and Test Run pages. It accounts for GraphQL server-based changes and numerous design related changes as dictated by #406.

Components which have been added/changed based on such includes:

  • Test Reports
    • Version related identifiers have been removed
    • Run History now shown per test
  • Test Queue - Admin View
    • Manage Assistive Technology Versions
    • Add Test Plans to the Test Queue
  • Managing Assistive Technology Versions Modals
    • Scenario 1 - Adding a New AT Version Modal
    • Scenario 2 - Edit an Existing AT Version Modal
    • Scenario 3 - Removing an Existing AT Version - Danger Modal
    • Scenario 4 - Adding an Existing AT Version
    • Scenario 5 - Removing an AT Version already in use - Warning Modal

Known Issues

  • Flicker when saving result of AT and Browser Details modal
  • Test Reports client query not supported
  • Anonymous Test Run client query not supported
  • Confirmation dialogs with editing and creating actions with Manage Test Queue Component

Copy link
Contributor

@alflennik alflennik left a comment

Choose a reason for hiding this comment

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

Looks good just a couple little comments

@howard-e howard-e force-pushed the new-manage-test-queue branch 2 times, most recently from 9c27ecf to c1f0018 Compare May 25, 2022 21:08
howard-e and others added 26 commits May 26, 2022 15:09
@howard-e howard-e requested review from evmiguel and alflennik May 26, 2022 20:37
@howard-e howard-e changed the title Add New Manage Test Queue Component Update Test Reports, Test Queue and Test Run pages May 26, 2022
Copy link
Contributor

@alflennik alflennik left a comment

Choose a reason for hiding this comment

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

I'll need to continue reviewing this, I feel like I only got through 10% of all the capabilities we've added and I know a few more are incoming too. Here are a couple of thoughts I did have which hopefully are helpful.

onChange={handleDateAvailabilityTextChange}
onKeyPress={handleDateAvailabilityTextKeyPress}
maxLength={10}
/>
Copy link
Contributor

Choose a reason for hiding this comment

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

I was able to sidestep the validation by pasting in some arbitrary text. This is admin-only so it may or may not be worth the effort to account for that.

Also you can hit submit at any time, even if the admin forgot to type in a date (in which case there is an internal error). This also may or may not be worth the effort to address. I do know keeping this component simple was a goal of the design.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@alflennik good points! I had initially overlooked such validation at the time with the plan to return to it and never did, so thanks for pointing that out.
I've now pushed commits which should include proper feedback to these situations. Please check again when you can

@@ -204,7 +249,7 @@ const AtAndBrowserDetailsModal = ({
</ModalSubtitleStyle>
</legend>
{/* Tester Scenario 1 */}
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm leaning towards removing these "scenario x" labels because I think issue 406 won't be actively maintained going forward, but the code will be. So I predict there'll be future scenarios or alternate scenarios that will make the scenario numbers lose their usefulness. That said, Isaac does have some pretty extensive documentation for the feature so I could be swayed to change my opinion.

@isaacdurazo isaacdurazo self-requested a review May 27, 2022 21:46
Copy link
Member

@isaacdurazo isaacdurazo left a comment

Choose a reason for hiding this comment

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

This is a test. Please ignore, Howard 😅

Copy link
Member

@isaacdurazo isaacdurazo left a comment

Choose a reason for hiding this comment

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

Another test.

@howard-e howard-e marked this pull request as ready for review May 31, 2022 14:51
@howard-e howard-e force-pushed the new-manage-test-queue branch from a7a3907 to 48f7025 Compare May 31, 2022 18:30
Copy link
Contributor

@evmiguel evmiguel left a comment

Choose a reason for hiding this comment

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

@howard-e (great job!) and I walked through the code together. I tested the different scenarios as well. Changes from #423 have also been added to this PR.

@evmiguel evmiguel merged commit 3ba26ed into main May 31, 2022
@evmiguel evmiguel deleted the new-manage-test-queue branch May 31, 2022 19:20
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.

4 participants