Common convention for invoking unit tests across a python project?

Question

Is there a standard convention, or even a growing one, around where and how to invoke the tests associated with a project? In many projects, I'm seeing it bundled into a Make, a separate test.py script at the top level of the project, etc to do the work.

I looked around for some common thing with setup.py, but didn't spot anything there (granted, I didn't look hard). What's common and best practice?

score 1 · Accepted Answer · edited May 23 '17 at 11:47

1

The short answer is yes, there's a simple convention built-in to the unittest module. See this previous question.

edited May 23 '17 at 11:47

Community

1
1

answered Jul 24 '10 at 17:42

Cerin

60,957
96
316
522

Why not this: `import x; x.test()`? Pardon the semicolon. – Hamish Grubijan Jul 24 '10 at 17:52
If you read my link, you'll see how the unittest module does that for you. – Cerin Jul 24 '10 at 18:27
So the convention is to put a test.py at the root of your project that does all the relevant imports and invokes them with unittest.main() ? – heckj Jul 24 '10 at 18:46
@heckj, Yes, assuming all your unittest-containing files are structured as a Python package accessible from test.py. – Cerin Jul 25 '10 at 01:55

Common convention for invoking unit tests across a python project?

1 Answers1