Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Version 5.1.0 fails the test cases
See original GitHub issueLatest version of the package fails test cases. This can be explored with https://npm.runkit.com/react-pdf-js. React version to 16.9.0 and Node version 10. It throws an error SyntaxError: Unexpected token export.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (2 by maintainers)
Top Results From Across the Web
java.lang.NoClassDefFoundError: kotlinx/coroutines/test ...
DescribeSpec tests work fine. Upgrade to 5.1.0 and now all the tests are failing with: java.lang.NoClassDefFoundError: kotlinx/coroutines/ ...
Read more >Why Your JUnit 5 Tests Are Not Running Under Maven
There is a very common issue preventing your JUnit 5 tests from running under Maven. In this post, I explain why and provide...
Read more >Why Your JUnit 5 Tests Are Not Running Under Maven - DZone
So your JUnit 5 tests are not running under Maven? Do you have JUnit 5 tests that run fine from your IDE but...
Read more >Unit Tests are getting failed in Java 8 to Java 11 Migration
I'm working on migrating my project from Java 8 to Java 11. So I used, Spring 5.1.0, Java 11, Eclipse 4.16 and Tomcat...
Read more >JUnit 5 How to Repeat Failed Test - Software Test Academy
It just retries your tests without checking their results, in order to add some logic and retry the tests when they are failing,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Facing same issue in Version 5.5.1 with react 16.12.0. Any solution or workaround?
Fixed in the latest version