Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Ticket #3090 (new defect)

Opened 12 years ago

Last modified 10 years ago

UI issues - Causes of failures are difficult to track down

Reported by: schake Owned by: wehart
Priority: normal Milestone:
Component: FAST Version: FAST 1.2
Keywords: Cc:

Description (last modified by wehart) (diff)

Example comments from Zoltan:

  • When tests fail, it would be useful for us to be able to find out why.

Can the test harness report why the failure occurred (no answer files, no
zdrive output files, differing checksum, etc.)? Where are the zdrive stdout
and stderr stored (so we can look for segfaults, etc., when no output is
produced)? Can/Should? they be stored in the common run directory above?

Attachments

Change History

comment:1 Changed 12 years ago by schake

The test driver already adds an exit_status.

It should also add an exit_comment above this, which can be set to notify why something failed. This allows some logic processing by the parser which can be carried over, instead of relying completely on the analysis section of FAST.

comment:1 Changed 10 years ago by jdsiiro

  • Priority changed from high to normal
  • severity normal deleted

Converting all severities into priorities and deprecating the severity field.

comment:2 Changed 10 years ago by wehart

  • Version changed from alpha to FAST 1.2
  • Description modified (diff)
  • Milestone set to FAST 2.0

We should explore whether this is related to the XUnit output generation.

comment:3 Changed 10 years ago by wehart

  • Milestone changed from FAST 2.0 to FAST 2.1

comment:4 Changed 10 years ago by wehart

  • Milestone FAST 2.1 deleted
View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as new
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.