Fix stem_memory coverage reporting and raise threshold#16
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Package publishing
Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation. |
Summary
stem_memoryunit tests that exercise every factory inmemory_factories.dartInMemoryBroker.disposeand fallbackBroker.close)stem_memoryworkflow coverage threshold from0to80Verification
cd packages/stem_memory && dart testcd packages/stem_memory && dart test --coverage=coverage --fail-fastcd packages/stem_memory && dart run coverage:format_coverage --lcov --in=coverage --out=coverage/lcov.info --report-on=libcd packages/stem_memory && dart run ../../tool/coverage/coverage_badge.dart --lcov coverage/lcov.info --out coverage/coverage.json --min 80Closes #14