-
Notifications
You must be signed in to change notification settings - Fork 280
test(core-kernel): increase coverage to 100% #3593
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
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #3593 +/- ##
===========================================
+ Coverage 75.07% 76.18% +1.11%
===========================================
Files 448 448
Lines 10178 10184 +6
Branches 1315 1315
===========================================
+ Hits 7641 7759 +118
+ Misses 2515 2404 -111
+ Partials 22 21 -1
Continue to review full report at Codecov.
|
|
|
Summary
core-kernelpackage tests, fixes #3474. Couple of problems though:MemoryQueue
There is unhandled promise rejection and there is no way to handle it or to report error to caller.
Then there is also problem with
lastResultswhich is passed as argument toprocessFromIndexand at the same time kept as private field. It's mutable array and it's unclear why it's being passed around. Also there is no way to get thoselastResultsback. I could not find a single usage to determine the intent.Another problem is with
lastQueuefield. It's set in couple of places but isn't ever read. As result callingresumeseveral times will rerun same task again.ClassManager
It has
driversfield and functions to extend that. But that field isn't used during instantiation increateDriverfunction. I removed those. I could instantiate new instances on my own, but usual implementation throughcreateDriverNameDriveris asynchronous. As forgetDriversmethod there is no way to return classes that might be created throughcreateDriverNameDriver.I guess it was refactored to support async creation and class instantiation wasn't removed completely:
Checklist