document how to run the test suite #386

Merged
merged 2 commits into from Jan 21, 2015

Conversation

Projects
None yet
3 participants
@greg0ire
Contributor

greg0ire commented Apr 18, 2014

I read in the issues that you were using cram. I think the command to run for running the tests is cram tests/*.t, but I'm not sure because 3 out of 5 tests fail.

@ggreer

This comment has been minimized.

Show comment Hide comment
@ggreer

ggreer Jun 26, 2014

Owner

make test should do the trick, provided you have the dependencies. You should get 2 failing and 8 passing test cases. Those two failures are for known issues.

I'll close this once I document the test stuff.

Owner

ggreer commented Jun 26, 2014

make test should do the trick, provided you have the dependencies. You should get 2 failing and 8 passing test cases. Those two failures are for known issues.

I'll close this once I document the test stuff.

@commonquail

This comment has been minimized.

Show comment Hide comment
@commonquail

commonquail Jul 14, 2014

Contributor

Tangent: It looks like the TLS certificate for the Cram site expired three days ago and Firefox seemingly no longer allows me to continue (Chromium does), but Cram can be installed via pip and should then work as noted in the previous comment:

sudo apt-get install -y python-pip && \
sudo pip install cram

I think including the last line in a relevant location (the readme or the wiki) is a good idea. While arguably redundant (it's already on the Cram site), having to launch a browser to discover this seems unnecessary, and I expect the risk of that information becoming outdated is very low.

NB: I have alerted the site owner of the problem.

Contributor

commonquail commented Jul 14, 2014

Tangent: It looks like the TLS certificate for the Cram site expired three days ago and Firefox seemingly no longer allows me to continue (Chromium does), but Cram can be installed via pip and should then work as noted in the previous comment:

sudo apt-get install -y python-pip && \
sudo pip install cram

I think including the last line in a relevant location (the readme or the wiki) is a good idea. While arguably redundant (it's already on the Cram site), having to launch a browser to discover this seems unnecessary, and I expect the risk of that information becoming outdated is very low.

NB: I have alerted the site owner of the problem.

greg0ire added some commits Apr 18, 2014

@greg0ire

This comment has been minimized.

Show comment Hide comment
@greg0ire

greg0ire Jan 20, 2015

Contributor

ping @ggreer I just rebased

Contributor

greg0ire commented Jan 20, 2015

ping @ggreer I just rebased

ggreer added a commit that referenced this pull request Jan 21, 2015

@ggreer ggreer merged commit 251211f into ggreer:master Jan 21, 2015

1 check passed

continuous-integration/travis-ci The Travis CI build passed
Details
@ggreer

This comment has been minimized.

Show comment Hide comment
@ggreer

ggreer Jan 21, 2015

Owner

I totally forgot about this PR, but I'm glad the tests have gotten so much better since it was opened.

Owner

ggreer commented Jan 21, 2015

I totally forgot about this PR, but I'm glad the tests have gotten so much better since it was opened.

@greg0ire

This comment has been minimized.

Show comment Hide comment
@greg0ire

greg0ire Jan 21, 2015

Contributor

@ggreer totally forgot about it too, and yesterday I decided to review my opened P.R. :)

Contributor

greg0ire commented Jan 21, 2015

@ggreer totally forgot about it too, and yesterday I decided to review my opened P.R. :)

@greg0ire greg0ire deleted the greg0ire:test_suite_documentation branch Jan 21, 2015

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