Zephyr Enterprise Feature Requests

Probelm Statement : There is test case name inconsistency between JIRA BDD plugin and ZE Vortex automation. In case if a scenario has 2 Examples table rows, then JIRA BDD plugin will create 2 test cases with identical test names, e.g. "scenario" and "scenario". While in case if test cases are being created through Vortex for the same type of scenario, they will have different names, e.g. "scenario" and "scenario 2".   For Cucumber 7 which we are using right now in our framework, here is the naming conventions: “Scenario - Example #1.1”, “Scenario - Example #1.2”, etc. Previous version of JIRA BDD Plugin,  it was creating test cases for all Examples table rows with the SAME name, which was inconstant with how Cucumber default JUnit report was doing, which was giving some indexing to each test case name. Due to this , when we are executing BDD testcase created (containing exdample tables) from JIRA  using zephyr, results being attched to same testcase .   Current and expected testcase naming snapshots are attched   Reference : Case #00535844: Test Case name inconsistencies between JIRA BDD Plugin and Vortex automation   ... View more

Zephyr has the ability to execute Automation Test Runs using TestComplete or TestExecute. This is a useful platform to control test runs and import results into Zephyr. However the Vortex option on Zephyr feels a little under developed. It would be nice to have this developed further to allow the scheuling of test runs. For example:-   - Run test 1 - Every Monday at 2am - Run Test 2 - On the 2nd of every money at 2am - Also include a Automation Test Run Execution list of all the jobs scheduled and a log of those executed.   Is it possible to include this feature? ... View more