Forum Discussion
Thanks for your reply, but it doesn't work for me. :smileysad:
I think mine is test item, but not project item, so /projectitem:Item1 doesn't work for me at all.
All I want is to run specific Test item with command line, seems there isn't a way for that....
/test: Script|RunQSOO|Main, this is not what I want, as I don't want to specific a script unit
- tristaanogre7 years agoEsteemed Contributor
Because your test item is in sub-folders, you need to include the full pathing/grouping as per https://support.smartbear.com/testcomplete/docs/working-with/automating/command-line-and-exit-codes/command-line.html#command-line-arguments
So, based upon your screenshot, you should do a command line something like
<program file path>\TestComplete /run /project:QSOO /test:Group|Sub|Item1
- snie17 years agoContributor
Thank you Martin for your post.
Unfortunately I have tried to use the full path before, and right now again, it doesn't work neither.
My Command: /run /p:QSOO /test:"Group|Sub|Item1"
I am wondering if TestComplete does support this? The answer seems "YES" from the document, but always fail for me which drive me crazzzzy.....
- tristaanogre7 years agoEsteemed Contributor
Next question:
Are you sure that you have the correct MDS file over on the machine running TestExecute? The test items and their hierarchy are stored in the MDS file. So, if you have done editing on one machine in TestComplete but haven't made sure that your target machine running TestExecute has the latest source version, then you'll never get them to run because, according to TestExecute, they don't exist.
Related Content
- 6 months agosohailalam2696
- 12 years agomaxthomassin
- 5 years agonish_b
Recent Discussions
Check PopupMenu exists
Solved2 days agomfoster711- 3 days agosimonaferrara
- 3 days agomacheshmeh