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

Page/Component Object refactor; Added new tests for Landing/Home/Sign-in pages #997

Open
wants to merge 18 commits into
base: main
Choose a base branch
from

Conversation

aasimsyed
Copy link
Contributor

Contributor checklist


Description

  • updated Playwright

  • ignored tests/results/reports from watch

  • added an html reporter for axe

  • updated components and pages with id locators for use in tests

  • refactored the page object model design, updated page/component objects, tests for landing, home, and sign-in pages

  • added a utility method to run accessibility tests on any given page

  • tested locally

Related issue

  • #ISSUE_NUMBER
    N/A

Copy link
Contributor

github-actions bot commented Oct 27, 2024

Thank you for the pull request!

The activist team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Development rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

  • The TypeScript and formatting workflows within the PR checks do not indicate new errors in the files changed

  • The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

  • The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

Copy link

netlify bot commented Oct 27, 2024

Deploy Preview for activist-org ready!

Name Link
🔨 Latest commit 9f518de
🔍 Latest deploy log https://app.netlify.com/sites/activist-org/deploys/673896a0bb06120008510cec
😎 Deploy Preview https://deploy-preview-997--activist-org.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@aasimsyed aasimsyed changed the title Test/refactor pom add update components nav signin Page/Component Object refactor; Added new tests for Landing/Home/Sign-in pages Oct 27, 2024
@andrewtavis andrewtavis added the hacktoberfest-accepted Accepted as a part of Hacktoberfest label Oct 27, 2024
@andrewtavis andrewtavis self-requested a review October 27, 2024 19:48
@andrewtavis
Copy link
Member

Lemme know when this is ready for a final review, @aasimsyed :) Would be good to do a call this week as well, if it can work on your end 😊

@andrewtavis
Copy link
Member

Sorry for the wait on this, @aasimsyed! I'll write you on Matrix as well, but let me know if you'd like to do a call to fix the frontend checks, run the most recent version of the Playwright tests and then bring this in :)

CC @cquinn540 who expressed interest in looking into the tests a bit. Maybe the three of us can do a call?

@andrewtavis
Copy link
Member

One note on this is that the yarn.lock file is the current version from main as I didn't want to deal with the merge conflicts.

return (await this.page.locator("html").getAttribute("class")) ?? "";
}

public getLocator(selector: keyof typeof this.locators): Locator {
Copy link
Contributor

@cquinn540 cquinn540 Nov 16, 2024

Choose a reason for hiding this comment

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

Is there a reason we don't want to use locators the way Playwright recommends? https://playwright.dev/docs/locators

getLocator discourages that, and also encourages us to use ids to locate most of our elements as opposed to using roles and labels the way a user would.

@andrewtavis
Copy link
Member

Hey @aasimsyed 👋 Let me know if a call over the weekend to bring this in would work on your end, or if not when'd be a good time :) Hope you're well!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hacktoberfest-accepted Accepted as a part of Hacktoberfest
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants