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.

Sign up for GitHub

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

Jump to bottom

Improve TraceDiff Test Coverage #318

Closed
everett980 opened this issue Jan 25, 2019 · 0 comments
Closed

Improve TraceDiff Test Coverage #318

everett980 opened this issue Jan 25, 2019 · 0 comments
Assignees
@everett980

Comments

@everett980
Copy link
Collaborator

Requirement - what kind of business use case are you trying to solve?

Confidently make changes to files in src/components/TraceDiff. Lack of test coverage lowers confidence and adds overhead to features in this domain.

Problem - what in Jaeger blocks you from solving the requirement?

Absence of tests for most of this folder.

Proposal - what do you suggest to solve the problem or improve the existing situation?

Increase coverage for src/components/TraceDiff to 100% (within reason).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@everett980 everett980

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@everett980