Forum Discussion

Nasar's avatar
Nasar
Contributor
28 days ago

Test execn. outside Test Cycles _HELP

Hi all 

Is it possible to restrict users from executing Test cases outside Test cycle , we want to limit Test execution within Test cycle only .

Please share any knowledge , hopefully there is a solution other than asking users :). 

When Test cases are executed within Test cycle it's allows for better report results >

What are your thoughts Thanks in advance for your kind help - 

 

Let me pre-empt an answer  cheekily "no there is no such options available but if you add it as a suggestion someone at Smart Bear may pick it up at some point in the future :) " 

Zephyr Scale (general)
  • kristen32010's avatar
    kristen32010
    New Contributor
    22 days ago

    I agree! For us, it's the play button on the test cases within the Jira item itself. Some folks forget about the test cycle and just click that play button which creates the execution outside of the test cycle, and additionally there is no way to include that execution or pull it into the test cycle after its already been executed ad-hoc. Please give us an option to turn off ad-hoc executions!

    • Nasar's avatar
      Nasar
      Contributor
      22 days ago

      HI Kirsten this is exactly what's happening but I struggled to explain :) clearly .

      Test cases are being run from Jira , please Smartbear  can you provide an option whereby people are not able to execute test cases from Jira item _Please 

      Otherwise some reports where we are looking for Tags are useless,  Test cases are being run outside test cycles the Tag is returning as "NO_VAL" even when Tags are within Test cases .

      MisterB   apologies but Kirsten has articulated my case much better than i have done so far.

    • MisterB's avatar
      MisterB
      Champion Level 3
      25 days ago

      Hi Nasar, your 'cheeky comment' made me chuckle!

      I'm guessing you're talking about ad-hoc test cases - tests that have been created on-the-fly within a Jira Issue and executed outside of a Test Cycle.  These are a pain in the a$$ when it comes to reporting.  Looking at how this happens, the user first needs the ability to create a test case (before it can be executed), and it seems that this function can be controlled in Scale's permissions feature.  So perhaps that will work: disabling the ability to create test cases?

      I haven't tested it, but if you can access the Permissions feature (Project Settings > Apps > Zephyr Scale), you can experiment with setting permissions for the Create action, by User, Role or Group.

      If I've misunderstood your request, let me know!

       

      • Nasar's avatar
        Nasar
        Contributor
        25 days ago

        apologies I mean to say that in Zephyr scale users can run test cases without the  need to have a Test cycle ( people are able to run Test cases direct ) 

        Yes the correct thing to do is have the test cases executed  within a Test cycle>> Please Zephyr listen to us ( end users ) force people to create Test Cycle 

        Or at least give us an option to force users towards Test cycles . If some companies would rather continue to execute test cases direct then that's their choice  

  • duck-tester's avatar
    duck-tester
    Contributor
    26 days ago

    I have asked this question before as we have the same issue in our organisation. 

    unfortunately the only global setting there is currently is to thrn off the AI test helper (purple button in executions page)

    As you pre-empted this is a process thing for now. But if your suggestion gets some weight behind it they may do something about it. 

    I for one think all executions should happen within a cycle. And that’s a hard sell when the functionality to execute randomly with no cycle exists

    • Nasar's avatar
      Nasar
      Contributor
      25 days ago

      I sense your frustration and am guessing that I am not going to get any joy either .  Back in the old days Zephyr would have been able to quickly adapt they were flexible alas price of success makes them rigid :) 

    • MisterB's avatar
      MisterB
      Champion Level 3
      21 days ago

      I agree.  All executions should go through a test cycle.  It's critical to have that structure to ensure that reporting is consistent and accurate.  Let's hope this is resolved in a future release.

  • MisterB's avatar
    MisterB
    Champion Level 3
    25 days ago

    Ah.... so I think you're talking about the ability for the AI automation feature to execute tests directly from a test case, which I can see how that could happen.  I'm not using that tool at the moment but agree that it should be controlled - there's a cost element to it!