-
Notifications
You must be signed in to change notification settings - Fork 0
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
Tri 31401 e2e test stage #150
Conversation
tests/stage-test/cypress.config.js
Outdated
|
||
e2e: { | ||
|
||
baseUrl: 'https://oxi.matr.io/', |
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.
should it be stage url ?
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.
Thats rite, the stage scripts are not yet updated. Its created just as placeholder. Stage component ids and configurations ll be moved together in a new PR once we get to access Stage.
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.
Here is what I notice. The same tests are being repeated in "local", "stage", and "prod". Is there a way to reuse the same tests, with just the base url changing?
@mike-puzon-tri - We can have stage and prod together. But the component properties might be different in stage and prod, when new changes are pushed in stage and the tests would fail. The local can be left as how it is, within dev ui folder, as it has github action and intercepts in place. |
This covers prod tests and placeholder for stage scripts. Stage scripts to be updated with proper component ids etc., once the access is enabled