有没有一种简单、免费的方法可以在 Jira 中创建测试用例管理
我认为我唯一不明白的是你如何处理运行结果。因此，如果我在 Jira 中为测试用例设置一个新项目，我将如何制作它，以便我可以运行将测试用例标记为通过或失败，但不关闭 jira。
因此，我基本上希望原始 jira 始终处于打开状态，然后能够针对特定版本将其标记为通过或失败。原始的 jira 应该保持不变，只是以某种方式记录结果集？
我没有
任何意义的竹子
I think the only part I dont get is how you handle the run results. So if I set up a new project in Jira for test cases how would I make it so I can run mark a test case as pass or fail but not close out the jira.
So I basically want the original jira to be always open then be able to mark it passed or failed against a specific release. the original jira should stay unchanged just somehow log a result set?
I do not have bamboo
that make any sense
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（7）
我们在 Jira 中设置了一个简单的自定义工作流程，无需使用 Confluence。
我们添加了一种新的问题类型 - 测试用例。我们有一个新的子任务 - 测试运行。
测试用例只有三个工作流程操作：通过、失败和无效（最后一个是使测试用例多余的）。还有两种状态——开放和无效。
当测试用例通过或失败时，会自动创建测试运行。用户不手动创建测试运行。我们使用其中一个插件在转换时创建一个子任务。
测试运行可以处于通过或失败状态，并具有版本信息、通过或失败的用户以及评论。
就是这样。
以下是我用于设置 Jira 进行测试用例管理的一些链接：
We have setup a simple custom workflow in Jira without using Confluence.
We added one new issue type - Test Case. And we have a new sub-task - Test Run.
Test Case has only three workflow actions: Pass, Fail and Invalid (the last one is to make Test Case redundant). And two statuses - Open and Invalid.
Test Run is automatically created when Test Case passes or fails. Users do not manually create test runs. We use one of the plugins to create a subtask on transition.
Test Run can be in a Passed or Failed state and has version info, user who passed or failed and a comment.
This is it.
Here are some links that I used to setup Jira for Test Case Management:
我们遵循的方法如下：
我们使用 Confluence 来实现我们的测试用例。
每个测试用例都有自己的页面，描述设置、运行场景以及所有可能的结果。
我们有一个测试库页面，它是所有这些测试用例的父级。
当我们想要在特定版本上启动验证周期时，我们使用一个脚本
为汇合的每个测试用例生成相应的“测试运行”问题。
（@DennisG - JIRA 允许定义不同的问题类型，每种类型都有自己的工作流程）
摘要是测试用例的摘要
描述是测试用例的场景和结果
我们有一个特定的汇合链接引用测试用例
测试运行问题工作流程包含 4 个阶段
和 3 个解决方案
然后我们开始验证所有“测试运行”使用。
使用仪表板小工具可以很容易地看到有多少测试用例仍然需要运行，有多少被阻止，有多少已经完成，有多少失败了......
如果解决方案是“审查测试用例”，我们有能力调整测试用例本身。
结论 - JIRA 当然可以用作测试执行管理环境。合流，
作为一个维基提供了一个环境来构建必要的层次结构（技术，功能）。
最后一点。
我们开始广泛使用 Bonfire（JIRA 的插件）
http://www.atlassian.com/en/software/bonfire
这大大缩短了“手动”测试周期。
对我们来说，几周的投资回报率。
希望这会有所帮助，
弗朗西斯
PS。如果您有兴趣使用该脚本，请给我留言。
The approach we are following is as follows
We use Confluence for implementing our test cases.
Each test case has its own page describing the setup, the scenario to run and all possible outcomes.
We have a test library page which is the parent of all these test cases.
When we want to start a validation cycle on a particular release, we use a script which
generates for each test case in confluence, a corresponding 'test run' issue.
(@DennisG - JIRA allows to define different issue types, each with its own workflow)
The summary is the summary of the testcase
The description is the scenario and outcome of the testcase
We have a specific confluence link referring the testcase
The testrun issue workflow contains 4 stages
And 3 resolutions
We then start validating all 'test run' isuses.
Using dashboard gadgets it is easy to see how many testcases still need to be run, how many are blocked, how many have been done, and how many have failed ...
In case the resolution is 'review testcase' we have the ability to adapt the testcase itself.
Conclusion - JIRA is certainly usable as a test execution management environment. Confluence,
as a wiki provides an environment to build the necessary hierarchies (technical, functional).
Last point.
We start to extensively use Bonfire (a plugin for JIRA)
http://www.atlassian.com/en/software/bonfire
This shortens the 'manual' testing cycle considerably.
For us it had an ROI of a couple of weeks.
Hope this helps,
Francis
PS. If you're interested to use the script send me a note.
我们正在使用名为 informup 的测试用例管理。
测试用例管理与 Jira 集成。
此外，它完全集成在系统中，因此如果您想将其用作测试用例管理和错误跟踪系统，您也可以这样做
We are using this test case management called informup.
The test case management is integrates with Jira.
In addition it has fully integration in the system so in case you want to use it as a test case management and a bug tracking system you can do it as well
您可以使用 PractiTest，这是一个与 JIRA 集成的测试管理工具。 PractiTest 涵盖了您的整个 QA 流程，因此您可以使用它来创建需求、测试和测试集，并使用集成选项来报告 JIRA 中的问题。您还可以在不同实体之间进行链接。
详细了解 PractiTest 与 JIRA 集成
you can use PractiTest, a test management tool that integrates with JIRA. PractiTest covers your entire QA process, so you can use it to create Requirements, Tests and Test sets, and use the integration option to report issues in JIRA. you can also link between the different entities.
read more about PractiTest's integration with JIRA
老实说，我不确定使用 JIRA（或任何其他错误/问题跟踪工具）作为测试管理工具是一个好主意。问题在于问题跟踪器通常只有一个主要实体（问题），而测试管理工具通常区分测试用例和实际测试/结果。通过这种方式，您可以轻松地将相同的测试用例重复用于不同的版本，并存储测试结果的历史记录。测试运行和测试套件等其他实体通常也使管理和跟踪数据变得更加容易。因此，您可能需要考虑使用与 Jira 集成的专用测试管理软件，而不是使用 Jira 进行测试管理。有许多测试管理工具，包括开源项目：
http://www.opensourcetestmanagement.com/
您还可以查看我们的工具 TestRail，它还集成了 Jira：
http://www.gurock。 com/testrail/
http://www.gurock.com/testrail/jira-test-management.i .html
To be honest, I'm not sure that using JIRA (or any other bug/issue tracking tool) as a test management tool is a good idea. The problem with this is that issue trackers usually have a single main entity (the issue), whereas test management tools usually distinguish between test cases and actual tests/results. This way you can easily reuse the same test case for different releases and also store a history of test results. Additional entities such as test runs and test suites also usually make it a lot easier to manage and track your data. So instead of using Jira for test management, you might want to consider using a dedicated test management software that integrates with Jira. There are many test management tools out there, including open source projects:
http://www.opensourcetestmanagement.com/
You could also take a look at our tool TestRail, which also comes with Jira integration:
http://www.gurock.com/testrail/
http://www.gurock.com/testrail/jira-test-management.i.html
您是否尝试过查看 Jira 的插件目录 https://plugins.atlassian.com 以了解可用于扩展核心功能。那里可能有一些东西可以安装。
有一些工具结合了问题跟踪和测试管理（例如 elementool.com），但是如果您追求功能更丰富的问题跟踪体验，您可能需要开始寻找专用工具。
如果环顾四周后您发现没有合适的解决方案可以让您将东西集中在一个地方，您可能需要看看 TestLodge 测试用例管理，这是我开发的一个可以轻松与 Jira 集成的工具。
Have you tried looking in Jira's plugin directory at https://plugins.atlassian.com to see whats available to extend the core functionality. There may be something there that you could be installed.
There are tools out there that combine both issue tracking and test management (e.g. elementool.com), however if you are after a more feature rich issue tracking experience, you may need to start looking at dedicated tools.
If after looking around you find that there are no suitable solutions to enable you to have things in one place, you may want to take a look at TestLodge test case management, which is a tool I have developed that integrates easily with Jira.
为什么不直接将 JIRA 与测试管理工具集成呢？例如，我们使用 Kualitee。它与 JIRA 集成，并提供从报告的缺陷到底层测试用例和需求的可追溯性。因此，您可以在 Kualitee 上运行整个 QA 周期，并在 JIRA 中同步并将缺陷分配给您的团队。
您还可以生成测试用例执行报告和错误报告并将其导出，以便您在这方面也做好准备。
Why not just integrate JIRA with a test management tool? So, for example, we use Kualitee. It integrates with JIRA and provides traceability from the defect reported to the underlying test case and requirements. So, you can run your entire QA cycle on Kualitee and sync and assign defects to your team in JIRA.
You can also generate your test case execution reports and bug reports and export them so you are all set on that front as well.