-
Notifications
You must be signed in to change notification settings - Fork 394
fix: (CXSPA-9651) Continuum E2Es - Payment Methods #20158
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: (CXSPA-9651) Continuum E2Es - Payment Methods #20158
Conversation
Merge Checks Failed
|
357d56a
to
7757e47
Compare
spartacus
|
Project |
spartacus
|
Branch Review |
feature/CXSPA-9651-Continuum-E2Es---Payment-Methods
|
Run status |
|
Run duration | 04m 44s |
Commit |
|
Committer | Stanislav Sukhanov |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
3
|
|
2
|
|
0
|
|
107
|
View all changes introduced in this branch ↗︎ |
it('Page loaded', () => { | ||
cy.get('main').a11yRunContinuumTest(); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
weird, i've re-checked it I'll check again. Thank you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a race between the page loading and AccessEngine being setup. It might be safest to always wait for content to avoid flaky results.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's follow the naming convention.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure.
import { viewportContext } from '../../helpers/viewport-context'; | ||
|
||
describe('Payment Methods Page accessibility', { testIsolation: false }, () => { | ||
viewportContext(['desktop', 'mobile'], () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there are no different elements between the mobile and desktop versions, no need to run this twice.
|
||
it('Delete payment method', () => { | ||
cy.get('cx-card').first().find('button').click(); | ||
cy.get('main').a11yRunContinuumTest(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can just scan the modified element instead of the whole page again. Let's set the scope to just the unique card.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
roger that
it('set as default', () => { | ||
cy.get('cx-card').eq(1).find('button').first().click(); | ||
cy.get('.alert-success').a11yRunContinuumTest(); | ||
cy.get('main').a11yRunContinuumTest(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this test do anything different compared to the first main
scan?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope. It's just checking if there are no accessibility concerns after the change was made
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove the last thing since it's been checked previously
7757e47
to
8b0f407
Compare
There was a problem hiding this 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 minor nitpick. 😉
import { viewportContext } from '../../helpers/viewport-context'; | ||
|
||
describe('Payment Methods Page accessibility', { testIsolation: false }, () => { | ||
viewportContext(['desktop'], () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the desktop is the default, I think this might be redundant?
8b0f407
to
5dea72a
Compare
describe('Payment Methods Page accessibility', { testIsolation: false }, () => { | ||
before(() => { | ||
cy.a11yContinuumSetup(); | ||
cy.login('[email protected]', 'pw4all'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should import the credentials from local sample data files. There should be examples of this in other tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
before(() => { | ||
cy.a11yContinuumSetup(); | ||
cy.login('[email protected]', 'pw4all'); | ||
cy.visit('/my-account/payment-details'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I logged in with this user, there were no existing payment methods available. Did you create this user or find it from somewhere? Any new user would need sample data created so I'd check out using the standard user from sampledata to see if it has some payment details already there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
* introduced a new test suite for checking accessibility concerns for order history * addressed accessibility concerns found by a test. * closes: https://jira.tools.sap/browse/CXSPA-9651
* introduced a new test suite for checking accessibility concerns for order history * addressed accessibility concerns found by a test. * closes: https://jira.tools.sap/browse/CXSPA-9651
* introduced a new test suite for checking accessibility concerns for order history * addressed accessibility concerns found by a test. * closes: https://jira.tools.sap/browse/CXSPA-9651
* introduced a new test suite for checking accessibility concerns for order history * addressed accessibility concerns found by a test. * closes: https://jira.tools.sap/browse/CXSPA-9651
5dea72a
to
efe7883
Compare
introduced a new test suite for checking accessibility concerns for Payment Methods Page
closes: https://jira.tools.sap/browse/CXSPA-9651