Switch to Nose for testrunner

beeware / batavia

A JavaScript implementation of the Python virtual machine.

http://pybee.org/batavia

Other

1.39k stars 424 forks source link

Switch to Nose for testrunner #304

Open swenson opened 8 years ago

swenson commented 8 years ago

This has some advantages:

Auto-parallelization in CircleCI
Switch to jUnit XML output so that CircleCI will have better test result messages
Easier to collect names of tests, and other automation

freakboy3742 commented 8 years ago

Hrm... Personally, I'm not a big fan of Nose (or py.test for that matter). But I'd be interested to hear what others think.

swenson commented 8 years ago

I've had a hard time running out test suite under anything other than what we have. The logic to determine what constitutes a test by default is strange. I mostly want to be able to parallelize tests and collect the output in jUnit files, but I don't care so much what tool gets us there. Enumerating tests would also be nice. On Oct 16, 2016 8:12 AM, Russell Keith-Magee notifications@github.com wrote:Hrm... Personally, I'm not a big fan of Nose (or py.test for that matter). But I'd be interested to hear what others think.

—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

candeira commented 8 years ago

@swenson: would nose paralellise tests also locally? Example: my laptop has two cores, four if you count hyperthreading. Would tests run on all four HT cores if I ran the command in a particular way?

swenson commented 8 years ago

@candeira It does! I believe there is a flag you can use with nose to make it auto-parallelize.

adamchainz commented 8 years ago

I'm a pytest fan. You can parallelize on it with the pytest-xdist plugin.

One thing to consider is that Nose is effectively abandoned at this point, whilst development continues on pytest.