-
Notifications
You must be signed in to change notification settings - Fork 62
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
How do we run tests? #10
Comments
Would be good to have some tests, probably based on puppeteer and Browserstack. |
Thus far, I've run a simple webserver in the root directory
and tested manually via IronDB needs automated tests. Until I get around to this, pull requests graciously welcome. |
IIn the PR I did for using lodash functions instead of the whole library, I added a webpack-server to make the test in the browser easier using npm run serve. |
I saw that. That was great. So great, I added it back out of band. Thank you.
That would awesome; ImmortalDB needs automated tests. Do you have experience with Jest and/or Puppeteer? Would you be able to start on |
Sorry, for the delay in my response. |
Afaik there is jest-puppeteer to simplify the integration. |
Awesome. Tests will be sick. I have no experience with Jest nor Puppeteer, but let me know if/where I can |
Until automated tests have been built, the
|
I don't see any test script here in package.json. How are you guys running tests?
I think this should be added, also to maintain consistency accross the team we can add prettier and eslint.
Let me know your thoughts, I'm really excited about this
The text was updated successfully, but these errors were encountered: