Details
Improvement
Resolved
Minor
Description
public void myStep
{ throw new KnownFailure("CORBA down"); }If we threw the above from the middle of a step, JBehave could list the step as failing without stack trace in the outputs.
Activity
Mauro Talevi
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Paul Hammant [ paul ] | |
| Fix Version/s | 3.4 [ 17278 ] | |
| Description |
public void myStep {
throw new JBehaveKnownError("CORBA down"); } If we threw the above from the middle of a step (subclasses RuntimeException or AssertionError), JBehave could catch it, increment 1 for the Known error type (simply the message payload), and list the step as failing without stack trace in the outputs. It relies on the known-error state being succinctly communicated to (or determinable by) the steps class. For web-apps, stack-traces in web-pages are a common development choice. The stats aspect would be to report on the known error permutations for the run in summary form |
public void myStep {
throw new KnownFailure("CORBA down"); } If we threw the above from the middle of a step (subclasses RuntimeException or AssertionError), JBehave could catch it, increment 1 for the Known failure type (simply the message payload), and list the step as failing without stack trace in the outputs. It relies on the known failure state being succinctly communicated to (or determinable by) the steps class. For web-apps, stack-traces in web-pages are a common development choice. The stats aspect would be to report on the known error permutations for the run in summary form |
| Summary | Statistics and curtained stack traces for "known errors". | Statistics and curtained stack traces for "known failures". |
| Issue Type | New Feature [ 2 ] | Improvement [ 4 ] |
Separated suppressing of stack trace for known failures from the statistics collection, which should be dealt with in another issue.
Show
Mauro Talevi
added a comment - Separated suppressing of stack trace for known failures from the statistics collection, which should be dealt with in another issue.
Mauro Talevi
added a comment - Separated suppressing of stack trace for known failures from the statistics collection, which should be dealt with in another issue. Mauro Talevi
made changes -
| Summary | Statistics and curtained stack traces for "known failures". | Curtained stack traces for "known failures". |
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Description |
public void myStep {
throw new KnownFailure("CORBA down"); } If we threw the above from the middle of a step (subclasses RuntimeException or AssertionError), JBehave could catch it, increment 1 for the Known failure type (simply the message payload), and list the step as failing without stack trace in the outputs. It relies on the known failure state being succinctly communicated to (or determinable by) the steps class. For web-apps, stack-traces in web-pages are a common development choice. The stats aspect would be to report on the known error permutations for the run in summary form |
public void myStep {
throw new KnownFailure("CORBA down"); } If we threw the above from the middle of a step, JBehave could list the step as failing without stack trace in the outputs. |
Mauro Talevi
made changes -
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Mauro Talevi
made changes -
| Summary | Curtained stack traces for "known failures". | Curtailed stack traces for "known failures". |
Curtailed stack traces implemented. Throw a subclass of KnownException and no stack trace will appear.