-
Notifications
You must be signed in to change notification settings - Fork 19
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
[feature request]: Test coverage need to reach higher rate than today 70% #86
Comments
I am generally not happy with anything less than 100%, except for the few occasional code paths that are more costly to cover, than expert review. Those are rare, and usually involve impossible corner-cases/code paths that are their purely to make the compiler happy (ie; default cases in switch statements, or exceptional paths that should never be hit). Simple libraries should approach 100% coverage, but not at the expense of alternate path permutations through the code. Complete coverage != thorough testing. I am pleased to see the improvement in coverage though. |
I agree with you if we can do 100% that would be awesome. |
* #86 remove unused code * #86 adding unittest for DirectoryExensionTests * #86 imporve check content * #86 rename test class to share project and test check content * #86 adding coverlet msbuild for code coverage test * #86 gitingore encrypt file from test * #86 test UniqueKeyGenerator * #86 add exception to UniqueKeyGenerator * #86 fix test * #86 tmp allow test to check if it works * #86 update editor config with 2 space for csproj * #86 space intent * #86 remove unnec tags from AES example csproj * #86 temp ignore example test to check all tests for other os * #86 remove old and dead cli from docker test * #86 remove not wanted test * #86 update text messge for ignore,
We are at 85%, this will be closed, and move to #123 list than the scope of testing will be expanded as smaller features until it reachs its ultimum goal :) |
Contact Details
No response
Is your feature request related to a problem? Please describe.
not directly
Describe the solution you'd like
We want to imporve test coverage. Today it is aroud 70%, every thing 80% and up would be cool to reach.
Our ulitmate goal is to reach 100%.
Describe alternatives you've considered
No response
Additional context
No response
Priority Level
Low
Code of Conduct
The text was updated successfully, but these errors were encountered: