You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 23, 2020. It is now read-only.
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
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For a given tag
The text was updated successfully, but these errors were encountered: