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

[MILOLIBS RUN : MWPW-141223] Provide support to run nala tests on a given milo libs #240

Merged
merged 6 commits into from
Jan 12, 2024

Conversation

skumar09
Copy link
Contributor

@skumar09 skumar09 commented Jan 12, 2024

PR includes

  • Automation test scripts for the Personalization features actions
  1. Enhance the Nala tests framework or test template to run tests on milolibs
  2. Provide a GitHub action to support to run nala tests on different Env and Milo libs combination
  3. Examples:
    - https://main--project--owner.hlx.page/?milolibs=local (prod code, stage content)
    - https://main--project--owner.hlx.live/?milolibs=local (prod code, prod content)
    - https://feat-branch--project--owner.hlx.page/?milolibs=local (feature code, stage content)

Info :
.test.js file(s) will have following updates

const miloLibs = process.env.MILO_LIBS || '';
await page.goto(`${baseURL}${features[0].path}${miloLibs}`);

@skumar09 skumar09 added the run-nala Run Nala Test Automation against PR/Branch label Jan 12, 2024
@skumar09 skumar09 added run-nala Run Nala Test Automation against PR/Branch and removed run-nala Run Nala Test Automation against PR/Branch labels Jan 12, 2024
@JackySun9
Copy link
Contributor

Is this change impacting other tests?

@skumar09
Copy link
Contributor Author

Is this change impacting other tests?

@JackySun9 : No it won't impact other test, only Milo tests

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

Successfully merging this pull request may close these issues.

4 participants