I've posted with this suggestion. Hopefully it is addressed soon. https://community.smartbear.com/t5/TestComplete-Feature-Requests/Command-line-Execution-support-for-Zephyr-Folders/idc-p/193190#M2106
There's mention of Zephyr in here:
http://support.smartbear.com/testexecute/docs/running/automating/command-line/command-line.html
Thanks for the link. I think what I want to clarify:
1) Zephyr Folders are not mentioned as a command line input
2) These command line input do not create new Zephyr test cycles, what happens if you specify a Zephyr Test Cycle that does not exist?
3) If you were to create cycles beforehand using the Zephyr API (to address issues related to question 2) would you have to address the test cycle by ID (the Zephyr api documentation references that all cycles, folders, executions have unique ids)
4) If the command line input accepts cycle name, what happens if you have non-unique cycle names for a release version?
Here is a summary of what I've been able to find using the Test Complete command line (which is similar to Test Execute):
1) I cannot write results to a folder. I have been trying 'ZephyrFolder:' to follow the pattern set with 'ZephyrCycle:'
2) Referencing a test cycle that does not exist does not create a new one, in fact it does not seem to record it anywhere in Zephyr
3) You can reference any test cycle by name, no need to use execution ID
4) It seems to write to the most recently created test cycle. This is encouraging as I can create test cycles of the same name on an ongoing basis.
Executions to Folders is still an ongoing concern and if anyone has suggestions for incorporating the API calls for creating Zephyr Test Cycles into a pipeline/command line for Test Execute please let me know.
