-
Notifications
You must be signed in to change notification settings - Fork 209
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
Jest testing & test for add step #1366
Conversation
run it with npm run test-ui-2 |
Codecov Report
@@ Coverage Diff @@
## main #1366 +/- ##
=======================================
Coverage 66.23% 66.23%
=======================================
Files 125 125
Lines 2559 2559
Branches 400 400
=======================================
Hits 1695 1695
Misses 864 864 |
This is awesome. Following eagerly! Please ping me once the path is local. Great work! cc @harshkhandeparkar @vaibhavmatta @tech4GT and others! |
Could you add the run command to the overall test trigger so they run in Travis? |
@jywarren Do you know how can we make relative to examples/index.html ? |
ohk done with fs library as suggested by @harshkhandeparkar |
…travis but it will abort previous test-ui)
cc: @jywarren https://travis-ci.org/publiclab/image-sequencer/jobs/626434689#L1683 Horray!!! |
@jywarren Now we just need to add it to npm test-ui command properly . How can we do that? |
This is Awesome!!! Can you try breaking a test to be sure it triggers a Travis failure? 🎉🎉🎉 |
let's check with title |
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.
Great! Ok now we add it here;
Line 15 in 4a86abb
- npm run test-ui |
@jywarren travis failed as i changed title of page https://travis-ci.org/publiclab/image-sequencer/jobs/626440796#L1709 |
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.
Once we've merged, we can write an issue with a longer list of critical UI functions we want to test, and start getting gci folks to pitch in maybe!
Let's just remove a few of the console.log statements too and add a brief readme entry? Thanks, this is amazing!!!!! |
@jywarren LGTM |
Ah, I see a merge conflict, can you rebase? Then good to go!!!!! Thanks! |
@jywarren in which file? |
Oh sorry! Take a look - GitHub has marked the pr as having a conflict. It
should show which! But, you can rebase the whole branch to resolve it.
…On Tue, Dec 17, 2019, 6:47 PM keshav234156 ***@***.***> wrote:
in which file?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1366?email_source=notifications&email_token=AAAF6J5KJUQ6MQZIKIJKEVLQZFQIBA5CNFSM4J4BVROKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHELASI#issuecomment-566800457>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAF6J4VCHIBD2OPVKE5II3QZFQIBANCNFSM4J4BVROA>
.
|
@jywarren where it is shown in Github whether Pr is having conflicts Though i have updated the branch. Are merge conflicts still present sorry for asking stupid questions here.I have very lot of problems with git |
Ah! I dunno what happened, I saw a message earlier but now it's just asking for 2 reviews. I can bypass but let's aim for 2 in future PRs! Thanks! |
🎉🎉🎉🎉 awesome. Would you have interest in the list of tests issue and/or the readme update? This is so great!!!!! |
Ok will make list of ui test nedded.some of them are already listed in #1000 |
Fixes #1242
Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!
npm test
@publiclab/is-reviewers
for help, in a comment belowIf tests do fail, click on the red
X
to learn why by reading the logs.Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software
Please make sure to get at least two reviews before asking for merging the PR as that would make the PR more reliable on our part
Thanks!