TestContext is null when the test/fixture has a timeout attribute
Bug #654788 reported by
stathis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NUnit V2 |
Fix Released
|
Medium
|
Charlie Poole | ||
Bug Description
Using (2.5.7) create a test/fixture with a timeout attribute and try to access the testcontext object in the test of setup/teardown
The object is always null. Remove the timeout it works.
Related branches
Revision history for this message
| Charlie Poole (charlie.poole) wrote | #1 |
| Changed in nunitv2: | |
| assignee: | nobody → Charlie Poole (charlie.poole) |
| importance: | Undecided → Medium |
| milestone: | none → 2.5.8 |
| status: | New → In Progress |
| Changed in nunitv2: | |
| status: | In Progress → Fix Committed |
| Changed in nunitv2: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Applies to any test run on a separate thread, whether Timeout is used or not