Ignore run config and run everything

Class library usage, coding and language questions.
Posts: 1
Joined: Fri Dec 15, 2017 11:50 am

Ignore run config and run everything

Post by florian.mautendorfer » Mon Nov 19, 2018 3:13 pm

Hi everyone!

I was researching on how i can auto build and run my tests fromthe commandline and have almost everything set up.
What im missing is:
How can i execute the built ranorex solution exe but ignore the default run config? My goal is to always run every test case and smartfolder independent from the run config.

I have found the following but unstatisfying solutions:
1. Add an ALL run config to every rxtst file which needs to be maintained manually if folders change.
2. Code some python script or similar to check for all ids and make sure they are in the run config.

Im thinking there must be an easier solution but was unable to find something, but maybe someone on here has a solution for me?

Thanks in advance and BR

User avatar
Ranorex Guru
Ranorex Guru
Posts: 4041
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Ignore run config and run everything

Post by odklizec » Mon Nov 19, 2018 3:43 pm


Well, I think that RunAll configuration, is by far the easiest solution. But yes, it requires to be maintained ;) Luckily, there is also another solution. Just create a new code module in [Setup] section of test suite and put below code inside:
|_CheckAllTests.cs <-- here must be placed your code module.

Code: Select all

            var suite = (TestSuite) TestSuite.Current;
            IList<TestSuiteEntry> entries = suite.GetAllTestSuiteEntries();
            foreach(TestSuiteEntry entry in entries)
            	var testcase = entry as TestCaseNode;
            	if (testcase!=null)
            		testcase.Checked = true;
Basically, it enumerates and checks all test cases and smart folders of the test suite. Hope this helps? ;)
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration