Skip to content
This repository has been archived by the owner on Nov 23, 2020. It is now read-only.

ability to list all test functions #261

Open
lsbardel opened this issue Dec 1, 2016 · 1 comment
Open

ability to list all test functions #261

lsbardel opened this issue Dec 1, 2016 · 1 comment
Labels

Comments

@lsbardel
Copy link
Member

lsbardel commented Dec 1, 2016

For a given tag

@lsbardel lsbardel added the test label Dec 1, 2016
@carn1x
Copy link

carn1x commented Jul 27, 2017

Would this describe the ability to list and specify specific test functions as per this example?:

For instance in a current project I run -m runtests -l and get:

All test labels:

myapp.tasks

When actually what I'd hope to do is emulate the level of drill-down which -m unittest provides so I could list the following (and individually run any of):

All test labels:

myapp.tasks
myapp.tasks.SetQuantityTest
myapp.tasks.SetQuantityTest.test_gets_actor_quantity
myapp.tasks.SetQuantityTest.test_sets_actor_quantity

Currently at the moment only the following work:

-m runtests myapp
-m runtests myapp.tasks
-m runtests myapp.tasks.test_gets_actor_quantity

But not:

-m runtests myapp.tasks.SetQuantityTest
-m runtests myapp.tasks.SetQuantityTest.test_gets_actor_quantity

which seems kinda odd, and I suppose requires that all my test methods need to have unique names even across multiple classes? Is this a general assumption for all test suites or just pulsar's assumption? I've not encountered it before though.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants