StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGet name of current test in setup using nose
primarykey
Id
16710061
data
AcceptedAnswerId
16711038
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-05-23T09:21:06.953
FavoriteCount
1
LastActivityDate
2017-05-25T16:21:10.523
LastEditDate
2014-12-10T16:33:15.113
LastEditorUserId
771848
OwnerUserId
160206
ParentId
0
PostTypeId
1
Score
5
ViewCount
3140
LastEditorDisplayName
text
Body
I am currently writing some functional tests using nose. The library I am testing manipulates a directory structure. To get reproducible results, I store a template of a test directory structure and create a copy of that before executing a test (I do that inside the tests <code>setup</code> function). This makes sure that I always have a well defined state at the beginning of the test. Now I have two further requirements: <ol> <li>If a test fails, I would like the directory structure it operated on to not be overwritten or deleted, so that I can analyze the problem.</li> <li>I would like to be able to run multiple tests in parallel.</li> </ol> Both these requirements could be solved by creating a new copy with a different name for each test that is executed. For this reason, I would like to get access to the name of the test that is currently executed in the <code>setup</code> function, so that I can name the copy appropriately. Is there any way to achieve this? An illustrative code example: <pre><code>def setup_func(test_name): print "Setup of " + test_name def teardown_func(test_name): print "Teardown of " + test_name @with_setup(setup_func, teardown_func) def test_one(): pass @with_setup(setup_func, teardown_func) def test_two(): pass </code></pre> Expected output: <pre><code>Setup of test_one Teardown of test_one Setup of test_two Teardown of test_two </code></pre> Injecting the name as a parameter would be the nicest solution, but I am open to other suggestions as well.
Tags
<python><unit-testing><testing><nose><nosetests>
Title
Get name of current test in setup using nose
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USalecxe
UserOwnerUserId
1. USBjörn Pollex
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.