| Summary: | Run test multiple times | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Thom Hehl <thom> |
| Component: | TPTP | Assignee: | Torsten Stolpmann <stolpmann> |
| Status: | ASSIGNED --- | QA Contact: | Torsten Stolpmann <stolpmann> |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Thom Hehl
I think JUnit Theories/Assumptions, introduced with JUnit 4.4 might be something that helps you solve your problem within the framework itself (See http://junit.sourceforge.net/doc/ReleaseNotes4.4.html). I think this would be a much cleaner solution here. What do you think? Torsten No, because, in my circumstance, the test should NEVER fail. The failure indicates some criteria that I don't have nailed down and need to fix, but I can't recreate consistently. Then, once I've fixed it, it's hard to be certain it is fixed. |