-
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
feat: Implement tool to run provisioning script #148
base: master
Are you sure you want to change the base?
Conversation
b9289c1
to
65ed506
Compare
cy.reload(); | ||
getStartedModulesVersion().then(modules => { | ||
console.log(modules.map(module => module.id).filter(module => /^s.*$/.test(module))); | ||
expect(modules.some(module => module.id === 'skins')).to.be.true; |
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.
It would be better to check also the version of the module which is started to be sure that it the version of the module that we installed with the provisioning.
cy.waitUntil(() => cy.get('#provisioningMessage').should('not.be.visible')); | ||
cy.get('#provisioningResult').should('be.visible').should('not.be.empty'); | ||
// eslint-disable-next-line cypress/no-unnecessary-waiting | ||
cy.wait(5000); |
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.
Maybe a waitUntil would be better here, you should be able to call getStartedModulesVersion until you get the required module in the expected version.
Description
Implement tool to run provisioning script
...
Tests
The following are included in this PR
Checklist
I have considered the following implications of my change:
Documentation