<rss version="2.0" xmlns:a10="http://www.w3.org/2005/Atom"><channel><title>Inflectra Customer Forums: Spira Team Execution Status is updaed as Failed even the Test Passes (Thread)</title><description>&#xD;
Hello all,     Background: We are using Command line engine as Automation engine in Remote Launch to run Cucumber Test Scripts.     The problem is even after successful test case execution, for some cases the  Execution Status  in the SpiraTeam is updated to " Failed"  Status, instead of "Pass".   Whereas the  Test Results  show output results as success for the same test case.  This is happening for a particular type of  Test Cases which are meant to test Screen Validations/Error Messages.   How to solve this problem?      &#xD;
&#xD;
</description><language>en-US</language><copyright>(C) Copyright 2006-2026 Inflectra Corporation.</copyright><managingEditor>support@inflectra.com</managingEditor><category domain="http://www.dmoz.org">/Computers/Software/Project_Management/</category><category domain="http://www.dmoz.org">/Computers/Software/Quality_Assurance/</category><generator>KronoDesk</generator><a10:contributor><a10:email>support@inflectra.com</a10:email></a10:contributor><a10:id>http://www.inflectra.com/kronodesk/forums/threads</a10:id><ttl>120</ttl><link>/Support/Forum/spirateam/issues-questions/505.aspx</link><item><guid isPermaLink="false">threadId=505</guid><author>Riddhi Sharma (rsharma@skyscape.com)</author><title>Spira Team Execution Status is updaed as Failed even the Test Passes</title><description>&#xD;
Hello all,     Background: We are using Command line engine as Automation engine in Remote Launch to run Cucumber Test Scripts.     The problem is even after successful test case execution, for some cases the  Execution Status  in the SpiraTeam is updated to " Failed"  Status, instead of "Pass".   Whereas the  Test Results  show output results as success for the same test case.  This is happening for a particular type of  Test Cases which are meant to test Screen Validations/Error Messages.   How to solve this problem?      &#xD;
&#xD;
</description><pubDate>Tue, 12 Feb 2013 14:16:25 -0500</pubDate><a10:updated>2013-02-13T09:05:24-05:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/505.aspx</link></item><item><guid isPermaLink="false">messageId=936</guid><author>Riddhi Sharma (rsharma@skyscape.com)</author><title>We got the solution for this. Just wanted to share it here.  The Execution Status(for Command Line A</title><description>We got the solution for this. Just wanted to share it here.  The Execution Status(for Command Line Automation) is decided as:   Passed  – If automated test ran successfully and the results output to the console did not include any of the phrases – FAIL, ERROR, FATAL, WARNING, CAUTION  Failed  – If automated test ran successfully, but one of the phrases – FAIL, ERROR, FATAL – was included in the console output  Caution  – If automated test ran successfully, but one of the phrases – WARNING, CAUTION – was included in the console output  Blocked  – The automated test did not run successfully  So, if the  NAME of the Test Case  contains any of the reserved phrases like "ERROR" or "FATAL" or "WARNING" or "FAIL" or "CAUTION" then the execution status is updated to FAILED even when the test had passed.  In ours case, test case name was containing  "error"  phrase which lead to the mentioned issue.  To conclude, the following phrases MUST NOT be used in the test case name:    FAIL, ERROR, FATAL, WARNING, CAUTION     &#xD;
&#xD;
</description><pubDate>Wed, 13 Feb 2013 09:05:23 -0500</pubDate><a10:updated>2013-02-13T09:05:23-05:00</a10:updated><link>/Support/Forum/spirateam/issues-questions/505.aspx#reply936</link></item></channel></rss>