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

Increase Unit Test Coverage >= 90% #39

Open
kb1lqc opened this issue Feb 4, 2018 · 2 comments
Open

Increase Unit Test Coverage >= 90% #39

kb1lqc opened this issue Feb 4, 2018 · 2 comments

Comments

@kb1lqc
Copy link
Member

kb1lqc commented Feb 4, 2018

We currently have about 79% coverage for a unit test. Let's bring that test coverage above 90%!

Coveralls Data

Coverage Status
https://coveralls.io/github/FaradayRF/faradayio?branch=master

Files to Test

Unit Test Files

Coverage Report Generation

We use coveralls-python to generate coverage reports. The .coveragerc file defines that we only test the module faradayio and our travis.yml file specifies the coverage test on line 11

The issue ticket documenting adding unit test coverage with coveralls is #30 which could be of help when working with the tools.

@kb1lqc
Copy link
Member Author

kb1lqc commented Feb 28, 2018

An observation: Unit Testing the run() function could automatically test the monitorTUN() function as well.

https://coveralls.io/builds/15714182/source?filename=faradayio/faraday.py#L217

@kb1lqc
Copy link
Member Author

kb1lqc commented Mar 1, 2018

@hdkmike, @reillyeon, @nedbat I'm seeing odd operation of coverage

https://coveralls.io/builds/15752681/source?filename=faradayio/faraday.py

The above coverage report agrees with my local use of coverage. It's pretty clear that the run() code is not being included in the coverage test output. This is odd because I am using --concurrancy=thread and also using the Threading.thread module as the documentation suggests.

I also attempted to use --timid with no effect.

  • Heck, this appears to be an environment specific issue per coveragepy #582

I'm at a loss here. I will probably remove this ticket from the current project and keep it on the backburner. It may even make me look at asyncio again now that the TUN code is working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant