Hello,I've got a project suite withz several projects which runs properly under TestComplete 8.6 under Windows XP but when I try to run it via TestExecute (I try to run the first project of the suite) I get a "The element to be run was not specified" error for the first test. I do not see my application get started, I get immediatelly the test results shown and what's even more, TestExecute claims that 2 of 29 tests were run and both were ok.The same suite ran a few days ago with some Windows 7/x64 issues which I started to fix now and wanted to test if those fixes work properly. On XP it still works but on Win 7 x64 it fails with this error message.Any suggestions? The message has no further details.GreetingsMarkus

Hello,another small test also failed: I added a Log.Message('something'); as first statement of the routine of the first test to be run. The message didn't appear in the log. It's only the same "The element to be run was not specified".The complete project suite was copiued over from the TestComplete PC 1:1 and put on the same drive/folder structure. Running TestExecute with administrator privileges doesn't help either.GreetingsMarkus

What is the command line you are using to run what you want to run?

Hello,I don't use the commandline I run the tests like this:1. start TestExecute by its icon2. open the project suite via it's Systray context menu3. I run the first project of the suite by the same context menuNow I get immediatelly a Internet Explorer session opened which displays the test results page and claims that 2 tests out of 29 have ben run successfully.See my 2 attached images. I also tried to open that first project alone now, butthe run menu item suggests that he's loaded the whole project suite anyway.Why is this?Could it be that something corrupted some path inside one of my project files?If yes, where to look at?GreetingsMarkus

The attached images seem to be missing. I'll try to add them now.

Hi,This problem can occur if the test to be executed is not specified for the test item. Suppose that your project has one test item that has two child test items and you do not specify the test for the first child test item (see the attached image - TestItemsPage.PNG). If you run this project, you will have the "The element to be run was not specified" message in the test log (see the attached image - TestLog.PNG).So, to solve the problem, check if all the test items in your project have associated tests.

Test Execute issue: "The element to be run was not specified"

12 Replies

markus_humm
Occasional Contributor
14 years ago
Hello,

another small test also failed: I added a Log.Message('something'); as first statement of the routine of the first test to be run. The message didn't appear in the log. It's only the same "The element to be run was not specified".

The complete project suite was copiued over from the TestComplete PC 1:1 and put on the same drive/folder structure. Running TestExecute with administrator privileges doesn't help either.

Greetings

Markus
tristaanogre
Esteemed Contributor
14 years ago
What is the command line you are using to run what you want to run?
markus_humm
Occasional Contributor
14 years ago
Hello,

I don't use the commandline I run the tests like this:

1. start TestExecute by its icon

2. open the project suite via it's Systray context menu

3. I run the first project of the suite by the same context menu

Now I get immediatelly a Internet Explorer session opened which displays the

test results page and claims that 2 tests out of 29 have ben run successfully.

See my 2 attached images. I also tried to open that first project alone now, but

the run menu item suggests that he's loaded the whole project suite anyway.

Why is this?

Could it be that something corrupted some path inside one of my project files?

If yes, where to look at?

Greetings

Markus
markus_humm
Occasional Contributor
14 years ago
The attached images seem to be missing. I'll try to add them now.
Abramova
Staff
14 years ago
Hi,

This problem can occur if the test to be executed is not specified for the test item. Suppose that your project has one test item that has two child test items and you do not specify the test for the first child test item (see the attached image - TestItemsPage.PNG). If you run this project, you will have the "The element to be run was not specified" message in the test log (see the attached image - TestLog.PNG).

So, to solve the problem, check if all the test items in your project have associated tests.
markus_humm
Occasional Contributor
14 years ago
Hello,

thanks for your tip, but I cannot see this in my project. See my attached screenshot. TestExecute complaints fot the TC20 testcase already

and I cannot see the issue you described.

Greetings

Markus
tristaanogre
Esteemed Contributor
14 years ago
When you "copied" your project to your other machine to run, did you make sure you copied over all the files? If you're sharing Script code units between projects, copying over a single project folder may not copy over all the files. You need to make sure that all your related files, paths, folders, in the same general folder structure on the TestComplete machine, are copied over to the TestExecute machine.
markus_humm
Occasional Contributor
14 years ago
Hello,

I copied over the folder containing everything related to that project suite. Means all project folders, all log folders, all project suite project files. Simply everything. I might try to strip this project suite down to one project tomorrow, after doing a good backup of the XP machine but I#m not yet convinced this really does it.

The suite contains some projects shich are "ticked off" currently but that shouldn't matter when I select a single project to run in TestExecute.

Greetings

Markus
Abramova
Staff
14 years ago
Hi,

According to your screenshot, the TC20 test runs correctly. The "The element to be run was not specified" informative message corresponds to the parent test item - 101_Anmeldung. This message is posted for the same reason as that I described - the test to be executed is not specified for this test item. However, it is just an informative message, not an error, and the issue with the uncompleted project run is unlikely to be connected with this message.

TestComplete may stop the project execution prematurely if you use the Runner.Stop method in your tests. For example:

if Sys.OS == Vista then Runner.Stop

This code explains why TestComplete runs the project on Windows XP successfully, and why it stops the project run on Windows Vista prematurely.

Please make sure that you do not use this method in your tests.

If you still face the problem, could you please send us your project suite?
markus_humm
Occasional Contributor
14 years ago
Hello,

I do not use the runner stop method. The TC20 testcase doesn't properly run, because it never starts the tested app and I already hat a log.message as first statement in the called procedure but it's text never appeared in the log. It seems it never really called the procedure.

I can send you the TestSuite if you guarantee to handle it with the necessary confidentially.

WHich e-mail address would I need to send it to? And: it's quite big.(1 GB uncompressed)

I could send you a download link.

Greetings

Markus