Bob_C
Contributor
Joined 2 years ago
User Profile
User Widgets
Contributions
Re: Test Cases for a Jira 'FIX IN' version
Kudos to Andy for talking through this in a sidebar conversation. I ended up submitting a help ticket to SmartBear, and did get some feedback. I went through the description that you gave and believe that the below steps will help in retrieving the Zephyr Scale Test Cases that are associated with the Jira Issue for a specific fix version. 1. You can use the JQL query first to get all the Jira Issues linked to that specific fix version Eg: Project = DEMO AND fixVersion = "FIX IN" 2. Create and save the above search query as a filter. 3. Navigate to Reports -> Traceability Report in the Zephyr Scale section 4. Try to filter by "Issue" and choose the filter that you created above 5. Choose the Traceability Direction as Coverage -> Test Cases 6. Generate the report The report generated will include all of the Jira issues related with that version, as well as the Zephyr Scale Test Cases that are linked to those Jira issues. This was successful in generating a report that shows all test cases, which helped quite a bit. However, I was not able to create a test cycle automatically from this list of test cases. It still would require a manual operation of selecting test cases (and not missing any along the way). In further communication with SmartBear support, I found that there was not a way to do this directly through their UI, and they suggest that I submitted a feature request. I submitted this feature request, and am hoping it will get some traction to get it implemented.49Views1like0CommentsTest Cases for a Jira 'FIX IN' version
How can I find all Test Cases that will be associated with a certain Jira 'FIX IN' version? We have a number of Jira issues that are associated with a Jira 'FIX IN' Version. Each Jira issue has at least one test case linked to it. How can I get a test case list based on the issues in each version? We have 200+ stories (issues) and therefore 200++ test cases. The next build will address 50+ stories(issues) and I would like to look at only these test cases. There are 2 use cases that I want for this: Review all of the case statuses to make sure that they are all in APPROVED status Create a test cycle for this build that encompasses only what is testable, and not items not yet implemented. We have been able to handle this in the past by manually picking the test cases, but I can see this getting complicated very quickly with the number stories / test cases we have so far. I am trying to look ahead with managing bug-fix mode in future builds, which will have their own set of test cases linked to each bug.Solved128Views0likes1CommentSearch for Comments in a Test Case
Is there a way to search for/export all comments in a group of test cases? We were thinking about using comments in our test cases for documenting items we may want to look at later, or may need some more clarification. Having to open each individual test case and looking at comments is tedius and prone to missing comments. I have seen similar threads on this (some many years old) and it does not appear that there is a way to do this. How do others do this?Solved125Views0likes3CommentsAtlassian Team24
Not sure if this is the right forum for this. I will be attending the Atlassian Team 24 conference in Las Vegas April 30-May 2, 2024. This is my first time there, so I am not sure exactly what to expect. I am hoping to have the opportunity to meet others that use Zephyr Scale. I am hoping to be able to talk, show, discuss and banter about what has worked (or not worked) for others with Zephyr Scale. This community forum helps and is good, but is much different than having a conversation. Let me know if you are going, i would like to meet up and talk.36Views1like2CommentsRe: JQL Search for Estimated Time is NULL / BLANK
I was able to talk to a coworker and he helped figure this out. Wanted to let other's know the solution. I found out that you can find estimated time ranges within the query. project = MGS and issue in coveredByTestCasesHavingField("estimatedTime", "00:00" , "00:05") project = MGS and issue in coveredByTestCasesHavingField("estimatedTime", "00:05" , "99:59") Query 1 will give estimated times <= 5 minutes, and Query 2 will give estimated times >= 5 minutes. Armed with this knowledge, we realized we can find empty estimated times by finding anything outside the 0 to 99 hour range. project = MGS and issue NOT IN coveredByTestCasesHavingField("estimatedTime", "00:00" , "99:59") This method requires that a test case is linked to an issue. There may be another way to do this, I am interested to hear if there are other solutions, or better yet if there is a way to do this within Zephyr without needing to be linked to an issue.171Views1like0CommentsJQL Search for Estimated Time is NULL / BLANK
Is there a way to do a query/filter on estimatedTime that has not yet been entered? I was able to find this information: https://support.smartbear.com/zephyr-scale-server/docs/en/jql-functions.html#UUID-bb04c337-22d6-fee6-7703-b4515a68234c_N1697097036420 I saw this example in the documentation and it seems to work as expected, but is limited to only filter an exact value: project = MGS and issue in coveredByTestCasesHavingField("estimatedTime", "03:00") I would like to use this to find all issues with test cases where the estimatedTime has not yet been entered. I tried using synatax of ("estimatedTime", NULL) and ("estimatedTime", BLANK) and these did not work. I also used ("estimatedTime", 00:00) but this is not the same as it not being entered. As a follow-on related question: is there a way to use this to search for estimatedTime > 00:05 or < 00:05 as an example?Solved136Views0likes1CommentRe: Burn Down Charts
Butch, I am still working with them on this. They have requestied a lot of our data, which is hard for me to provide. We are on data-center due to our security requirements and getting them full sets of project data they requested is not easy. This issue seems pretty obivous to me, and I even mentioned in my communications to them about you having the same issue. Are you on cloud? They may be able to see your data easier if you open a similar ticket. In digging into this, I have found that there may be a couple of (non-ideal) workarounds available. When you generate a report, you can export all that data into excel. From there you could potenially manipulate the data into a semi-useable form. In Jira, there is a way to create your own dashboard gadget, and there are zephyr dashboard gadgets that match the zephyr reports. I am ASSUMING that there would be a way to create your own gadget that would create correct burn-down charts. Both of these would require extra-ordinary effort to do, and something that I would expect SmartBear to provide out-of-the-box.125Views1like0CommentsRe: Determine Amount of Effort (time) Remaining
Andy, Thanks for the response. I thought I missed something, as I would expect to see this basic info available in the Zephyr reporting tools. What you proposed is an OK workaround for a deficiency in Zephyr reporting capability.19Views0likes0Comments