More lightweight testing setup about glastopf HOT 7 CLOSED

Well I used this big input set for the clustering. I suggest to add some parameters to the test script so you can choose which tests you are running (focus on the parts you changed).

from glastopf.

I do not use the test script, try Nose it blows your mind (and your nose).
I'll try to create some modification to test_dorks, i would really much like testing to work "out of the box" - without manually seeding of the database. It might be dramatic, so i will do in a pull :)

from glastopf.

I decided to use unittest back in the days because it's a build-in module and I needed as few external modules as possible (all test cases are created during the DARPA CFT project). I wouldn't mind switching to Nose :)

from glastopf.

Oh, but nothing needs to be changes to use Nose. It is just a advanced
testrunner - it works with the tests in the repo as of now

On Sat, Jan 12, 2013 at 8:45 PM, Lukas Rist [email protected]:

I decided to use unittest back in the days because it's a build-in module
and I needed as few external modules as possible (all test cases are
created during the DARPA CFT project). I wouldn't mind switching to Nose :)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/22#issuecomment-12183217.

from glastopf.

Heh, marvelous! Looking forward to the new test runner!

from glastopf.

Will take some days or a week. Introducing dependency injection to simplify the whole dork thingy to make it more testable (and maintainable)...

from glastopf.

fixed with #24 - testing now completes much faster. I recommend using nosetests instead of the htmltestrunner.

jkv@asterix:~/glas-dev/glastopf$ nosetests 
...............
Ran 31 tests in 36.324s

jkv@asterix:~/glas-dev/glastopf$ 

from glastopf.