Forum Discussion
Sorry, my bad. The original line does not have it (ugh, smileyface proves it hehe):
"C:\Program Files (x86)\SmartBear\TestExecute 12\Bin\TestExecute.exe" "D:\_work\r3\a\AccessControl.FrontEnd\TestScript\AccessControl\AccessControl.pjs" /r /p:AccessControl_FE /test:DEV_AccessControl_FrontEnd /e /exportLog:"C:\Temp\Log_FE.mht"
- tristaanogre7 years agoEsteemed Contributor
Another dumb question I know... perhaps 2 dumb questions.
1) The screenshot shows the project in the editor of TestComplete. Is your attempt to run in TestExecute on the same machine as that screenshot or a different machine?2) If it's on a different machine, can you verify that you have the latest copy of the MDS file on that second machine? The MDS is the file that stores those test items.
- marinb7 years agoContributor
Valid questions. Different machine, correct project though.
I solved the problem by using /u:smokeTest /rt:smokeTest... instead of /test:<testitem calling the smokeTest function in the smokeTest script unit>
However, I am still curious why the proposed way does not work.
- tristaanogre7 years agoEsteemed Contributor
So, the project MDS file has been copied from the development machine to the test machine and still not recognized. That is curious because, technically, it should work (my manual attempt to reproduce works).
Glad the workaround is doing what you need it to...
Just as a curiousity thing... what happens if you shorten the name of the test item? Perhaps there's a maximum string length or something on the command line (I don't see why, but stranger things have happened).
Related Content
Recent Discussions
- 14 hours agodhundley