Update DMS unit tests
Estimation
Story points: 3 SP
Estimated focus duration (perfect conditions): 10 days
Estimated pessimistic duration (worst case scenario): 16 days
Description
Click to expand
Who
- @CaptainFaisal -- developer
- @dagiopia -- advice and help related to the requirements, reviewer
- @dagiopia @kabir.kbr @janaina.senna -- architectural definitions
What
- Review and fix unit tests already implemented in DMS that are not working because DMS code was changed and the unit tests are not reflecting it.
How
- Run current unit tests implemented in DMS.
- Review and fix unit tests that are not running successfully.
- Run all the unit tests to guarantee they are passing successfully.
Why
- To keep DMS maintainable and healthy.
- To reduce technical debt.
When
- No technical dependencies.
Acceptance Criteria
Click to expand
- Merge request
- Code review
- Unit tests fixed
Work Breakdown Structure (WBS)
Task | Description | Duration | Status | Start Date | End Date | Comment |
---|---|---|---|---|---|---|
A | Run current unit tests and evaluate error messages for potential solutions | 6 Hrs | Done | 7th Nov | 7th Nov | |
B | Implement solutions to broken CLI unit tests (non-onboard related) | 8 Hrs | Done | 8th Nov | 12th Nov | |
C | Implement solutions to broken libp2p unit tests | 12 Hrs | Paused | 14th Nov | ||
D | Implement solutions to broken utils unit tests | 7 Hrs | Done | 17th Nov | 21st Nov | |
E1 | Implement solution to broken internal/messaging unit test | 6 Hrs | Paused | 21st Nov | ||
E2 | Refactor UpdateKadDHT function to not use global 'db' variable | 6 Hrs | Paused | 24th Nov | 28th Nov |
Edited by Faisal Dulaimy