Provide direct native support for getting NUnit test results into Zephyr Enterprise without hassle
Please add native support for importing regular NUnit results files, as you've done for other testing tools' results files. Given we are a company that does a lot of C#/.NET development and uses and runs thousands of NUnit test cases When we reun our NUnit test cases Then we should be able to import NUnit results directly into Zephyr Enterprise, without having to either: re-run the tests with special parameters, or use an external conversion tool to make the NUnit results look like JUnit results. Adding the requirement to run (or re-run) test cases with a lot of extra parameters (e.g. "--result=junit-results.xml;transform=nunit3-junit.xslt" which results in a non-standard NUnit result), or execute a third-party external conversion tool (potentially unsupported now), makes the process of importing NUnit results into Zephyr Enterprise much more complex than it needs to be. Using Zephyr Enterprise with NUnit should be easier / more convenient and support a standard workflow.
improve the triggering of test automation with github-actions
TLDR: As a user I can trigger the test execution manually by pressing the 'E' button. But I also want to trigger it from Github-actions. Therefore I would like Z.E. to automatically append testcases from test executions to the releaseTestScheduleId's parameter in the rest call I use to trigger the execution. Rest call can be found below: Background: I want to use Z.E. to manage my automated tests and want to use Github-actions to trigger the automated tests that are linked in a test execution. I only want to run the tests that are in the test execution to have full control of testing effort. In order to trigger test execution PR-001: from Github-actions we need to implement following Rest-request using the cURL obtained from Z.E. This will execute the tests that are defined in the test execution based upon the releaseTestScheduleId's. However, this is hardcoded and needs to be updated when adding or removing testscases to the test execution. e.g. if i add a new test to the execution, i need to manually include the releaseTestScheduleId to the testcaseExecutionList in this rest call. It would be nice if the releaseTestsScheduleId's in the testcaseExecutionList are not needed. It would be easier if i only need a link to the folder that contains the testcases. Or a redirect to this Get request could also give the releaseTestScheduleId's: This would mean that only the automated tests are run that are defined in the test execution without the need to manually update the Github-action. As a tester it would simplify testing.
Automation: Create separate Test Phases for each execution under the same Test Cycle
Currently, Vortex allows either reusing the same Test Cycle/Test Phase for all executions, or creating a new Test Cycle for each execution. However, as a User, I'd like to have Vortex creating separate Test Phases for each execution so that I can report on how many times the automation has been run. OLD ID :-ZENT-I-247
