Skip to content

feat(amazonq): UI Tests Baseline Framework Complete Set Up #7727

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

Merged
merged 40 commits into from
Jul 23, 2025

Conversation

laura-codess
Copy link

@laura-codess laura-codess commented Jul 21, 2025

Change

This is a large PR for all the baseline setup of the framework. It includes the auth, setup, 4 test suites and the abstractions for each, and the cleanup functions.


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

…as webpack.NormalModuleReplacementPlugin that needed to be there in order for the amazonq to compile
…he checks. have to commit to check since the build compiles with no errors
@avi-alpert
Copy link
Contributor

I recommend reorganizing the files by component that you're testing, for example a pinContext folder that has the test and related helper files in that folder. utilities shared by multiple tests (like generalHelper) can be moved to utils

@laura-codess laura-codess changed the title feat(amazonq): After Function Fix feat(amazonq): UI Tests Baseline Framework Complete Set Up Jul 22, 2025
@Hweinstock
Copy link
Contributor

From discussion, if one test fails we likely want some kind of general clean up util to ensure all the others don't. This may just be a reload window command? Might require some experimentation.

@Hweinstock
Copy link
Contributor

Don't see any blockers. I think the clean up can be done as a follow-up since atm I believe one test failing could cause the rest to fail.

throw new Error('No selectable login options found')
}

const companyItem = await findItemByText(selectableItems, 'Company account')
Copy link
Contributor

Choose a reason for hiding this comment

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

Why not do all of these without the varaiable assignment. Its making it hard to read.

Copy link
Contributor

Choose a reason for hiding this comment

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

is this what you're suggesting?

Suggested change
const companyItem = await findItemByText(selectableItems, 'Company account')
await findItemByText(selectableItems, 'Company account').click();

Copy link
Contributor

Choose a reason for hiding this comment

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

i think having it in two lines is more readable

Copy link
Contributor

Choose a reason for hiding this comment

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

We had an internal discussion. Spaces and comments should do it.

@laura-codess laura-codess merged commit 97397a8 into aws:feature/ui-e2e-tests Jul 23, 2025
31 of 37 checks passed
@laura-codess laura-codess deleted the after_function_fix branch July 23, 2025 14:39
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.

5 participants