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

warriors: update and activate commerce tests #418

Merged
merged 7 commits into from
Aug 16, 2024

Conversation

afmicka
Copy link
Contributor

@afmicka afmicka commented Aug 14, 2024

CORS issues for commerce prices and CTAs have been removed.
Updating and activating commerce tests for milo PRs.

MWPW-157416

@afmicka afmicka added the run-nala Run Nala Test Automation against PR/Branch label Aug 14, 2024
@afmicka
Copy link
Contributor Author

afmicka commented Aug 14, 2024

@Dli3 @JackySun9 @skumar09

Today has been merged to milo main the PR that removes CORS issues for commerce prices and CTAs on branches. I have updated and activated commerce tests so that they could run on PRs now. When i run locally, those tests are passing.

However, here they are failing the same as before. Does this repo needs some code syncing with milo repo? Do you have idea what could cause that the prices are still not visible for the run here?

One of the tests pages for example: https://main--milo--adobecom.hlx.live/drafts/nala/features/commerce/promo-placeholders (prices are visible now)

EDIT: they are failing only in chromium, but passing in firefox ?!

@Dli3 Dli3 added the @commerce label Aug 15, 2024
@afmicka
Copy link
Contributor Author

afmicka commented Aug 15, 2024

@Dli3 @skumar09 Skipped the tests for chromium. I see merch-block is also skipped some time ago, this issue for chromium is not new.

@@ -19,6 +19,8 @@ test.beforeEach(async ({ page, baseURL }) => {
});

test.describe('Commerce feature test suite', () => {
test.skip(({ browserName }) => browserName === 'chromium', 'Skipping tests for Chrome browser');
Copy link
Contributor

Choose a reason for hiding this comment

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

If this works locally for you, you could add a condition to skip if process.env.ci is true and it's running on chromium. This way, you can still run against chromium locally.
@afmicka

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@Dli3 did i add the condition wrongly? It did not help, failed here again.

Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like process.env.ci didn't work here. But if (browserName === 'chromium' && process.env.GITHUB_ACTIONS) test.skip() did.

@JackySun9
Copy link
Contributor

please fix all lint errors

@afmicka
Copy link
Contributor Author

afmicka commented Aug 16, 2024

Thanks @JackySun9 . Was trying different approaches with @Dli3 to skip tests only on github actions. We found the right one and all is good.

Once approved, will merge it.

@afmicka afmicka merged commit 4a78532 into adobecom:main Aug 16, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@commerce run-nala Run Nala Test Automation against PR/Branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants