Last Friday many of you sat in on the inaugural "Ask Jama," an hour-long web meeting that saw one of our consultants, Dennis Hodge, go over common uses of Jama's test management module. Thanks for joining us. Your participation definitely made the session! When we opened it up to questions from the audience, a couple dozen came in. Luckily some of them were repeats, but we couldn't get to them all with the time we had. Below you can find responses to the questions that went unanswered.Q&ACan I track planned versus actual test schedule?
If you'd like to suggest a topic for the next "Ask Jama" session, please comment on this post.
If you missed the session or want to view it again, here it is:
There isn't a report out of the box that does this. Each Test Plan can be tied to a release, but the individual test runs themselves do not have a way to track a due date. There is an included field for Execution Date for Test Runs. If you added a custom field to test runs for a Due Date and combined that with the execution dates, some creative custom reporting could enable you to track this.In every item type, we have the ability to see the status of the item but for a test case it is the automated system generated status of the execution, is there we can see if a test case is a draft or ready for execution?
The Status for Test Cases includes a roll-up of Test Runs results, so this cannot be changed. However, you could create a custom pick list that included these options. I recommend posting a Question in the community if you'd like to learn how others handle this.For continuous release projects is there a way to version a test case to show which release it supports?
Test cases themselves cannot be "versioned" in the standard Jama sense for use in another release. Versioning is used to track changes made to items. However, the Reuse tool is commonly used for branching test cases for use in different releases of a project. There is a discussion in the community
that might help you consider your options.Is there an enhancement in the Backlog to have one test case exist across multiple groups?
There is not currently such a feature planned in the roadmap. We recommend using Reuse if you would like to see a Test Case work in multiple groups.How do I import testcases/Requirements/Test runs from HP QC?
Jama offers an integration with HPQC through our Jama Integrations Hub. If you would rather manually support the use of cases and requirements from HPQC, we have an article that outlines what can be done with the SOAP API and our test management
features.Note that the next two questions apply to our global reports, the Test Plan Details report and the Test Plan Summary report.
I can't find a way to find the pre-conditions, post-conditions, and input to add into the report.
Neither of our global Test Plan reports include these fields. Depending on the complexity of the report needed, you may be able to build it with a Word template. If not, custom development with BIRT or Velocity
should enable you to design the reports you need.I am also interested to see how to produce test execution reports for a project based on the test cycle/week/Month etc.
Depending on the information you need, the above Test Plan reports might suffice. If they do not, you can create custom reports with BIRT or Velocity. We also offer custom report creation services—just check in with your Jama account manager.I'm interested in test outputs (test results, separate from test setup information).
Can you clarify what information is needed regarding outputs?What capability does Test Center have to add large attachments, pictures, or test data?
You can add attachments to a Test Run during the execution phase. We have a list of supported attachment and images types available here
.Is there or can there be a way to control what test case changes cause an existing test run to display the pencil / test case has changed icon? Some fields may not have an impact on the runtime context of a test, but it looks like any test case change (except for tags/attachments/links) causes a run to be out of date
no, there isn't a way to control what sets off the alarm for Test Runs being out-of-date. As you noticed it's the new Version being created that flags this feature. I understand where you're coming from here, though, and think this would make a great Idea to post in the community. It seems like something that would fit naturally in with the Item config screen, as you can select what fields set off the Suspect flag or what fields are set to Sync by default. If only there were another column for Test Run Current...Currently an item can be assigned to one release only. Multiple value for the attribute ‘Release’ is a must-have for our company because the failure tracking tool (JIRA) in use for the related mapped attributes are multiple value.
There isn't a way to allow more than one release to be assigned to an item, but I completely understand your need. I think it's for this reason many customers opt to Reuse test cases for different releases. If you'd like us to consider this as a feature, you can add an Idea to the community.How to “write” line breaks within a test step (e.g.; when using enumerations). Same applies for imports of test steps
There isn't a way to create the line breaks except with HTML (as this is what the Roundtrip feature does). The only suggestion I have is to use the
HTML tag.We also use step status ‘not performed’ for generic tests. Is it possible to add an additional step result ‘not performed’ to the existing ones (‘passed’, ‘failed’)? This step will get a comment reasoning it could not be performed, but shall not influence overall test run status.
There isn't a means to add an additional Result status, as there is a very particular calculation used in the rollup for the Test Case Status. Before starting formal test phases we use a checklist to check whether the system is ready for testing. Is it possible to create such a checklist in JAMA? Or is a JAMA Review the best place to address test prerequisites?
You hit the nail on the head here—it is preferred to send a test case, complete with prerequisites, to the review center. Generally speaking these are written into the Test Case in question. If you want something each tester can individually check off, it would make sense to include these as part of the Steps.Use Case: document gets exported (e.g.; via BIRT Report), customer changes document, and document gets imported again. Or is this handled as "new import"?
This would be considered a new import. At this time Roundtrip functionality works only for Excel documents.