Command Line Exe test automation
Posted: Mon Mar 30, 2015 9:37 am
Background to the problem:
I have a series of tests built in Ranorex Studio which work as expected.
Each test is set to continue on failure. When running in Ranorex Studio, these tests just continue even with a failure condition and provide the log at the end.
I need to be able to run the full test suite regardless of failures and just output the information from the command line. This will be used with TeamCity for automated nightly collation of results.
The Problem:
When I compile this into the executable file and run from the command line, the program appears to exit on the first failure (it encounters a -1 sig term when the first failure returns).
The Query:
Is this a bug in the compiled exe version or is this expected behavior?
If the compiled version is supposed to exit on first failure, is it possible to automate a full test suite from the command line when you just want to log faults?
Am I missing an additional set of parameters that tell the compiled exe to continue on faults?
Steps taken:
I have run the tests in Ranorex Studio successfully, verified each has a "continue on failure" option selected.
I have removed all of the previous compiled files and created a clean compilation.
I have tested at the command line in the same account and same privileges that Ranorex Studio is running as.
Any and all help very appreciated...
I have a series of tests built in Ranorex Studio which work as expected.
Each test is set to continue on failure. When running in Ranorex Studio, these tests just continue even with a failure condition and provide the log at the end.
I need to be able to run the full test suite regardless of failures and just output the information from the command line. This will be used with TeamCity for automated nightly collation of results.
The Problem:
When I compile this into the executable file and run from the command line, the program appears to exit on the first failure (it encounters a -1 sig term when the first failure returns).
The Query:
Is this a bug in the compiled exe version or is this expected behavior?
If the compiled version is supposed to exit on first failure, is it possible to automate a full test suite from the command line when you just want to log faults?
Am I missing an additional set of parameters that tell the compiled exe to continue on faults?
Steps taken:
I have run the tests in Ranorex Studio successfully, verified each has a "continue on failure" option selected.
I have removed all of the previous compiled files and created a clean compilation.
I have tested at the command line in the same account and same privileges that Ranorex Studio is running as.
Any and all help very appreciated...