Open blueyed opened 10 years ago
Mostly to avoid setup on @joelthelion's part and I wasn't sure if I was sticking to the tests. I've been using it to run tests on my own fork.
We should probably make CI testing an actual thing for this project.
We should probably use py.test instead of testify.
As stated on https://github.com/Yelp/Testify, Yelp is switching to py.test themselves and recommends using it. I haven't used testify myself, but am a fan of py.test.
Also, I have just noticed that testify does not appear to work on Python 3.4.
I'm in favor of switching to py.test as well. I only used Testify out of familiarity.
@joelthelion: Can you enable Travis builds for autojump please?
I've moved py.test migration into #300.
@joelthelion Ping. You would need to do step 1 and 2 of http://docs.travis-ci.com/user/getting-started/.
Thanks!
It seems like Travis builds are not enabled for this repo: https://travis-ci.org/joelthelion/autojump
Since there are some tests and a .travis.yml file already, it would make sense to make use of it.