Skip to content
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

Added Jest test and tweaked babel config a bit to make it work #348

Merged
merged 1 commit into from
Oct 29, 2020

Conversation

arielnmz
Copy link

@arielnmz arielnmz commented Oct 2, 2020

Added a very simple test in close.test.js that exemplifies the issue. I don't know about mocha or Karma but Jest is what I'm using and that's where I have the issue. I added the jest package to dev dependencies and also tweaked the babel config a bit to make Jest work. If you run the test using the command line e.g. jest close you will get a warning stating that

Jest did not exit one second after the test run has completed.

This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with --detectOpenHandles to troubleshoot this issue.

Same if you run them using WebStorm's Jest test runner, for example.

@pubkey
Copy link
Owner

pubkey commented Oct 18, 2020

Related pubkey/rxdb#2596

@pubkey
Copy link
Owner

pubkey commented Oct 20, 2020

@arielnmz I changed some code. Can you merge my change into the PR so we can se if this fixed the problem?

pubkey added a commit that referenced this pull request Oct 20, 2020
@pubkey pubkey closed this Oct 28, 2020
@arielnmz
Copy link
Author

Will do, sorry I got caught up in other stuff last week

@pubkey pubkey reopened this Oct 28, 2020
arielnmz pushed a commit to arielnmz/broadcast-channel that referenced this pull request Oct 29, 2020
Also added eslint jest env so it doesn't complain about missing symbols
@arielnmz arielnmz force-pushed the jest-test-never-ends branch from be38815 to 510a2ee Compare October 29, 2020 02:24
…#348

Rebased test commit to include new code

Also added eslint jest env so it doesn't complain about missing symbols
@arielnmz arielnmz force-pushed the jest-test-never-ends branch from 510a2ee to e0cb4e5 Compare October 29, 2020 02:25
@arielnmz
Copy link
Author

I just checked and it works now, thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants