These are chat archives for csu/pyquora

21st
Dec 2014
Christopher Su
@csu
Dec 21 2014 06:32
test
hi
Erwan
@aaronwinter
Dec 21 2014 06:34
Great!
Christopher Su
@csu
Dec 21 2014 06:34
haha this works great
Testing pyquora now with the new regex
and will then update on PyPi if it works
Erwan
@aaronwinter
Dec 21 2014 06:36
Ok, I think we should setup a TravisCl to automate testing whenever one of us make a pull request. If everything is working fine now we can create our tests based on your profile (two dashes), mine (only one) and Chris-Lu-6 for example
Isn't it, this platform rocks! :smile:
Christopher Su
@csu
Dec 21 2014 06:37
Sounds good. Want to just use unittest?
Erwan
@aaronwinter
Dec 21 2014 06:40
Travis has this nice badge that you can put on the README.md and does everything automatically but unittest would do the job as well I guess
Christopher Su
@csu
Dec 21 2014 06:40
I mean what should we write our test cases in?
Added the badge
Erwan
@aaronwinter
Dec 21 2014 06:49
I am reading the doc atm, not too sure if there is a special format that you can give to Travis or if we use unittest that Travis will automatically execute whenever there is a new pull request.
Christopher Su
@csu
Dec 21 2014 06:49
I've set it up already
Essentially, you have a travis.yml file that specifies things like setup before running tests and how to run the tests themselves
You can then have the tests be essentially anything that you could run in a virtual environment
So Makefiles work, tests written in unittest/nose/etc. all work
And on every build, Travis will just run the commands necessary
I'm deciding between unittest and nose now
Erwan
@aaronwinter
Dec 21 2014 06:50
Oh I see
Right now, it just runs tests/test_all.py which just does nothing
Alright, going with nose2
Actually, scratch that. Using nose
Erwan
@aaronwinter
Dec 21 2014 06:54
Ok, I am going to bed now. Ttyl!
Christopher Su
@csu
Dec 21 2014 06:54
Alright