You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like the TestRail CLI to be able to do?
Add parameter which will be responsible for keeping order of testcases as they are in the test suite. (and pay for it with longer import time)
Why is this feature necessary on the TestRail CLI?
Sometimes logic is that TCs are depended on order - in this case testrail is useless in term of investigation - it is only good for statistics (where one failed is still one failed not depended on order)
Some tools allows slightly different logic - that testsuite is actually bunch of testcases, and each TC consist of some atomic steps. But whole testsuite checks some complex functionality with setups on the start, some tests in the middle, teardowns at the end...
In this case it is also necessary to keep order of steps/TCs (setup TCs must be first, teardown TCs last...)
More details
Sample of input xml and how it looks when it is imported using this command ./trcli/bin/trcli -y -h https://instance.testrail.io/ --project "Autotest" --username USERNAME --password APIKEY parse_junit --title "import-test-order-sample" -f testrail-order-sample.xml
What would you like the TestRail CLI to be able to do?
Add parameter which will be responsible for keeping order of testcases as they are in the test suite. (and pay for it with longer import time)
Why is this feature necessary on the TestRail CLI?
Sometimes logic is that TCs are depended on order - in this case testrail is useless in term of investigation - it is only good for statistics (where one failed is still one failed not depended on order)
Some tools allows slightly different logic - that testsuite is actually bunch of testcases, and each TC consist of some atomic steps. But whole testsuite checks some complex functionality with setups on the start, some tests in the middle, teardowns at the end...
In this case it is also necessary to keep order of steps/TCs (setup TCs must be first, teardown TCs last...)
More details
Sample of input xml and how it looks when it is imported using this command
./trcli/bin/trcli -y -h https://instance.testrail.io/ --project "Autotest" --username USERNAME --password APIKEY parse_junit --title "import-test-order-sample" -f testrail-order-sample.xml
Interested in implementing it yourself?
No
The text was updated successfully, but these errors were encountered: