Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run 'fast' tests only #2026

Closed
takluyver opened this issue Jun 24, 2012 · 7 comments
Closed

Run 'fast' tests only #2026

takluyver opened this issue Jun 24, 2012 · 7 comments
Labels
Milestone

Comments

@takluyver
Copy link
Member

Running the test suite takes a couple of minutes. It would be handy to have a simple option to run only a subset of the tests in a fraction of that time. At a first pass, this could be everything except IPython.parallel.

@minrk
Copy link
Member

minrk commented Jun 24, 2012

I've wanted this for years (the twisted-based parallel tests were even slower than they are now).

A pattern that makes sense to me would be iptest does everything normal (exclude zmq, parallel), and iptest --all does everything.

@fperez
Copy link
Member

fperez commented Jun 25, 2012

Note that nose supports tagging of tests, numpy already uses that facility to tag specific slow tests. If it's an entire group of tests that's particularly slow we may instead omit whole groups, but I'd prefer tagging the slowest ones individually, so that even 'fast' runs provide at least some minimal coverage of all the pieces.

@minrk
Copy link
Member

minrk commented Jun 25, 2012

There are a few slow tests outside parallel, but since each parallel test creates and destroys a client, that is the bulk of the total time.

@fperez
Copy link
Member

fperez commented Jun 25, 2012

It's possible (though I'm not sure) that the nose tag mechanism could be applied to whole modules conveniently (the text exclusion tags do work at the function, class and module level). We need to look into that one.

@takluyver
Copy link
Member Author

The docs about tagging tests are here. It talks about tagging all the tests in a class, but not in a module or package.

@takluyver takluyver mentioned this issue Aug 2, 2012
Carreau added a commit that referenced this issue Aug 3, 2012
Fast Test

See #2026.

By default `iptest` will only run the faster tests, and `iptest --all` is necessary to run all of them. At present, it just cuts out `IPython.parallel`, but we can refine that if we want to.

`test_pr` is also updated so that you can pass extra arguments through to iptest.
@Carreau
Copy link
Member

Carreau commented Aug 3, 2012

Test time has been divided by 2. Is it enough to close this issue of do you want to cut more test ?

@takluyver
Copy link
Member Author

That was the intention of this, I just forgot the closes message in the commit. Closing now.

mattvonrocketstein pushed a commit to mattvonrocketstein/ipython that referenced this issue Nov 3, 2014
Fast Test

See ipython#2026.

By default `iptest` will only run the faster tests, and `iptest --all` is necessary to run all of them. At present, it just cuts out `IPython.parallel`, but we can refine that if we want to.

`test_pr` is also updated so that you can pass extra arguments through to iptest.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants