This is a migrated thread and some comments may be shown as answers.

Run test via fitnesse

3 Answers 80 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
dudi
Top achievements
Rank 1
dudi asked on 11 Aug 2011, 11:37 AM
Hi

I plan on running the tests recorded via a schedule job using a command running ArtOfTest.Runner.exe.
I need to know if the test pass or failed.
The only way I see is the results written to your custom file results.
Is there another way of getting the final test results?

Thanks

3 Answers, 1 is accepted

Sort by
0
Plamen
Telerik team
answered on 11 Aug 2011, 03:15 PM
Hello Dudi,

The .aiiresult file will be saved in the Project\Results folder by default. But you also have the option to set an alternative results output folder like this:   
"out=[folder path]"
Check the attached screenshot.

Hope this helps!

Greetings,
Plamen
the Telerik team
Vote for Telerik Test Studio at the Annual Automation Honors Voting!
0
Cody
Telerik team
answered on 11 Aug 2011, 03:43 PM
Hi Dudi,

Permit me to interject for a moment. In addition, ArtOfTest.Runner.exe process does return a code based on the general results of the test run. At this time these are the return codes defined:

/// <summary>
/// The command line runner exit code.
/// - '1' for processed run and tests success
/// - '0' for processed run but some failed tests
/// - less than 0 for not processed runs.
/// </summary>
public enum RunExitCode
{
    /// <summary>
    /// Run is processed and all tests passed.
    /// </summary>
    RUN_TESTS_SUCCESS = 1,
 
    /// <summary>
    /// Run is processed and some tests failed.
    /// </summary>
    RUN_TESTS_ERROR = 0,
 
    /// <summary>
    /// Run is not processed due to unexpected error.
    /// </summary>
    NOT_RUN_UNEXPECTED_ERROR = -1,
 
    /// <summary>
    /// Run is not processed due to compilation errors.
    /// </summary>
    NOT_RUN_COMPILATION_ERRORS = -2,
 
    /// <summary>
    /// No run to process, requested usage info.
    /// </summary>
    NOT_RUN_USAGE_INFO = -10,
 
    /// <summary>
    /// No run to process due to general invalid arguments error.
    /// </summary>
    NOT_RUN_INVALID_COMMAND_ARGS = -11,
 
    /// <summary>
    /// Run is not processed due to invalid test path argument.
    /// </summary>
    NOT_RUN_TEST_NOT_FOUND = -12,
 
    /// <summary>
    /// Run is not processed due to invalid test list path argument.
    /// </summary>
    NOT_RUN_TESTLIST_NOT_FOUND = -13,
}

Be aware we are going to change the numbers in our upcoming R2 release to work better with test runners & command line operation. RUN_TESTS_SUCCESS will be 0, meaning all tests were successfully run and all tests passed.

Greetings,
Cody
the Telerik team
Vote for Telerik Test Studio at the Annual Automation Honors Voting!
0
dudi
Top achievements
Rank 1
answered on 11 Aug 2011, 03:52 PM
Again right on the money

10X!!!
Tags
General Discussions
Asked by
dudi
Top achievements
Rank 1
Answers by
Plamen
Telerik team
Cody
Telerik team
dudi
Top achievements
Rank 1
Share this question
or