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.

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

Write tests for 100% code coverage #56

Closed
a5kin opened this issue May 3, 2019 · 1 comment
Closed

Write tests for 100% code coverage #56

a5kin opened this issue May 3, 2019 · 1 comment
Assignees
Labels
Milestone

Comments

@a5kin
Copy link
Owner

a5kin commented May 3, 2019

After adding so many features in version 0.2, we have broken coverage at ~96%. Need to write all necessary tests to bring it back to 100%.

@a5kin a5kin added the testing label May 3, 2019
@a5kin a5kin added this to the v0.2.0 milestone May 3, 2019
@a5kin a5kin self-assigned this May 3, 2019
a5kin added a commit that referenced this issue May 13, 2019
a5kin added a commit that referenced this issue May 14, 2019
a5kin added a commit that referenced this issue May 15, 2019
a5kin added a commit that referenced this issue May 15, 2019
a5kin added a commit that referenced this issue Jun 2, 2019
a5kin added a commit that referenced this issue Jun 2, 2019
a5kin added a commit that referenced this issue Jun 2, 2019
a5kin added a commit that referenced this issue Jun 2, 2019
a5kin added a commit that referenced this issue Jun 2, 2019
a5kin added a commit that referenced this issue Jun 3, 2019
@a5kin
Copy link
Owner Author

a5kin commented Jun 3, 2019

0.2 code is 100% covered with tests now. There was also an issue with tests failing at GTX 8xx series. It is resolved, was a bug in type casting.
We are a bit closer to the release, with only documentation issues left undone.

@a5kin a5kin closed this as completed Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant