-
Notifications
You must be signed in to change notification settings - Fork 101
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(storybook): cypress setup for the project #282
feat(storybook): cypress setup for the project #282
Conversation
Signed-off-by: User <shevkar.sanket@gmail.com>
@irmerk any updates on this? |
Signed-off-by: Matt Roberts <code@rbrts.uk>
No, I've added another commit which completes the basic setup. @rkotangoor @irmerk can you review, please? |
In theory, Cypress should now report the test results as comments in PRs, and the history will be publicly available at https://dashboard.cypress.io/projects/vrh5u7 |
@mttrbrts I have a question that the tests should be controlled via the main directory rather than the storybook package. Whats your opinion regarding this? |
That's a good question. For these E2E tests, we want to test the components in context (i.e. in an app), and so storybook is a convenient tool for that. I agree that we should be able to run the tests from a Unit tests for example are better suited to being situated local to the module / package that they are testing. |
@mttrbrts For unit tests you can have a look at this comment #14 (comment) |
Test summaryRun details
View run in Cypress Dashboard ➡️ This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
@sanketshevkar : could you add instructions to storybook Readme on how to run the cypress tests? Pretty much what you have included in this PR description? |
Sure would do that 👍. |
Signed-off-by: User <shevkar.sanket@gmail.com>
@mttrbrts @rkotangoor I've updated the readme file. |
This is awesome. @mttrbrts what kicks off the test run? Whenever a new PR is opened? |
|
@mttrbrts Shall we update this to Travis CI/CD pipeline plus |
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.
Needs investigation by @accordproject/maintainers-ui or @mttrbrts.
This is a separate issue. Let's focus on getting this change in first. |
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.
@sanketshevkar can you fix package-lock.json
, please? Otherwise, we're ready to merge this.
I'm not able to find where the merge conflict is exactly located. Can someone help me out? |
@sanketshevkar First of all update your branch. This will remove the |
Signed-off-by: User <shevkar.sanket@gmail.com>
Signed-off-by: Matt Roberts <code@rbrts.uk>
Signed-off-by: User <shevkar.sanket@gmail.com>
…ub.com/sanketshevkar/web-components into sanketshevkar/14/cypress-project-setup Signed-off-by: Matt Roberts <code@rbrts.uk>
Signed-off-by: User <shevkar.sanket@gmail.com>
Signed-off-by: Matt Roberts <code@rbrts.uk>
…ub.com/sanketshevkar/web-components into sanketshevkar/14/cypress-project-setup Signed-off-by: Matt Roberts <code@rbrts.uk>
@mttrbrts why is it expecting a dco of mine from some other id. I've made all my dco sign off's using shevkar.sanket@gmail.com. |
Apologies, I've been trying (and failing!) to fix this properly. I've now manually reviewed and approved the commits. |
@mttrbrts I've updated my branch and created new package-lock.json file. Should I commit that? |
No, problem. Thanks a lot for helping out. |
So, as of right now, we manually run this locally and it will produce a test result in Cypress? Next steps will be:
|
Yes, that's right. Although the PR integration is already setup (without using Travis or GH Actions). See #282 (comment) |
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.
👏🏻
Signed-off-by: User shevkar.sanket@gmail.com
Changes
npm run storybook
and once the storybook loads, on the second terminal within packages/storybook runnpm run cypress:open
. Cypress app would start and select the markdownEditor.spec.js file and then the test should start.Flags
lerna clean && lerna bootstrap && lerna run build
as a new devDependency is added.Screenshots or Video
https://www.loom.com/share/72e05a6e0c014ba6940fb36b757580a8
Related Issues
Author Checklist
--signoff
option of git commit.master
fromfork:branchname