Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Add venv & interestingness tests#36

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

@jschwartzentruber
Copy link
Collaborator

This adds tests to make sure setup.py doesn't break, and that interesting tests work as expected.

Calling LithiumTests.test_arithmetic in the venv also ensures that we can call interestingness scripts by path (not part of the lithium module).

This is a cleanup of some of the travis/appveyor tests@nth10sd came up with in#28 &#33 by porting them to unittests.

(passing in py2, failing in py3)Tests that setup.py works, and installed interestingness tests can be used in an installed environment.These are mostly ported to unittests from@nth10sd's work here:*MozillaSecurity#28*MozillaSecurity#33
@jschwartzentruberjschwartzentruber removed the request for review fromnth10sdAugust 2, 2017 00:22
@jschwartzentruber
Copy link
CollaboratorAuthor

This passes except for the fileIngredients unicode problems discussed in#33.

@nth10sd
Copy link
Contributor

Looks good so far, sans me nitpicking theif sys.platform.startswith("win") portion as we had discussed. I forgot our conclusion about using theplatform module though.

@jschwartzentruber
Copy link
CollaboratorAuthor

Good call. We agreed to use platform.system() consistently. I'll push the update after#39 lands so the tests go green :-)

@jschwartzentruber
Copy link
CollaboratorAuthor

The virtualenv test is failing on Travis due to system module differences. I'll have to investigate.

@codecov-io
Copy link

Codecov Report

Merging#36 intomaster willincrease coverage by12.26%.
The diff coverage is94.02%.

Impacted file tree graph

@@             Coverage Diff             @@##           master      #36       +/-   ##===========================================+ Coverage    68.6%   80.87%   +12.26%===========================================  Files          15       15                 Lines        1497     1563       +66     ===========================================+ Hits         1027     1264      +237+ Misses        470      299      -171
Impacted FilesCoverage Δ
setup.py0% <0%> (ø)⬆️
lithium/tests.py95.15% <96.92%> (+0.02%)⬆️
lithium/lithium.py79.87% <0%> (+0.12%)⬆️
interestingness/ximport.py73.91% <0%> (+4.34%)⬆️
interestingness/envVars.py25.64% <0%> (+25.64%)⬆️
interestingness/timedRun.py62.26% <0%> (+62.26%)⬆️
interestingness/crashes.py88.88% <0%> (+88.88%)⬆️
interestingness/outputs.py95.23% <0%> (+95.23%)⬆️
interestingness/range.py96.29% <0%> (+96.29%)⬆️
... and2 more

Continue to review full report at Codecov.

Legend -Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing data
Powered byCodecov. Last update21a3f0b...3119a71. Read thecomment docs.

@jschwartzentruber
Copy link
CollaboratorAuthor

I will split this into separate PRs, since the interestingness tests are much simpler.

jschwartzentruber added a commit to jschwartzentruber/lithium that referenced this pull requestAug 28, 2017
@nth10sdnth10sd mentioned this pull requestAug 29, 2017
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@jschwartzentruber@nth10sd@codecov-io

[8]ページ先頭

©2009-2025 Movatter.jp