blocks|key|2086572|text|我在Jira+Cloud上遇到了XRAY，我发现它真的很有用，我已经开始在我们公司使用，并取代了zephyr。X射线将使您有机会在一个单一的界面中维护手动测试和自动测试。它支持Rest，因此您可以从jenkins导入结果并更新jira问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2086573|https://marketplace.atlassian.com/plugins/com.xpandit.plugins.xray/server/overview|offset|length|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2A|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@$D|N|E|O|1|P]]|A|$]]]|F|$G|$5|H|I|J|A|$K|C]]]]

I came across XRAY on Jira Cloud and i found its really usefull, I have started using in our company and replaced zephyr . Xray will give the opportunity to maintain both manual and automated test in one single interface. It support Rest api so you can import results from jenkins and update jira issues also.

<a href="https://marketplace.atlassian.com/plugins/com.xpandit.plugins.xray/server/overview" rel="nofollow noreferrer">https://marketplace.atlassian.com/plugins/com.xpandit.plugins.xray/server/overview</a>

blocks|key|251950|text|如果你试图将规范和测试联系起来，那么你就错了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|251951|如果你是正确使用黄瓜，规格是测试。|251952|我建议你从务实的程序员那里得到“黄瓜书”，里面有很多关于如何有效使用这个工具的好东西。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

If you are trying to associate specs with tests, then You're cuking it wrong.

If you are using cucumber right, the specs ARE the tests.

I'd suggest you get 'The Cucumber Book" from the Pragmatic Programmers. Tons of good stuff in there about how to use the tool effectively.

blocks|key|252011|text|试试http://relishapp.com+(我创建的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|entityMap|0|LINK|mutability|MUTABLE|url|http://relishapp.com/^0|2|K|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@$A|L|B|M|1|N]]|C|$]]]|D|$E|$5|F|G|H|C|$I|J]]]]

Try <a href="http://relishapp.com" rel="nofollow">http://relishapp.com</a> (which I founded).

blocks|key|2086491|text|我会考虑使用一个票务管理系统，如Trello，Jira，或者Pivotal+Tracker或TestLink。我希望使用与管理新特性、任务和bug相同的系统。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I would consider using a ticket management system such as Trello, Jira, or Pivotal Tracker or TestLink. I would look to use the same system that I am using for managing new features, tasks and bugs.

blocks|key|251984|text|使用Test，您可以将测试用例与它们的自动化类方法链接起来。看看这个screencast：http://testcollab.com/blog/screencast-test-automation-with-test-collab/，它演示了测试用例与PHPUnit_Selenium包的集成。同样，黄瓜也可以被整合。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|251985|我们还没有自动调度功能--但您可以这样做：|251986|通过由Jenkins触发的API在test上创建测试执行。一旦分配了测试执行，tests将自动触发您的黄瓜测试。|251987|免责声明:我是测试Collab的联合创始人。|entityMap|0|LINK|mutability|MUTABLE|url|http://testcollab.com/blog/screencast-test-automation-with-test-collab/^0|19|1Z|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@$A|R|B|S|1|T]]|C|$]]|$1|D|3|E|5|6|7|U|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|V|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|W|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]]]

With Test Collab, you can link test cases with their automated class methods. Take a look at this screencast: <a href="http://testcollab.com/blog/screencast-test-automation-with-test-collab/" rel="nofollow">http://testcollab.com/blog/screencast-test-automation-with-test-collab/</a> It demonstrates integration of test cases with PHPUnit_Selenium package. Similarly cucumber can be integrated too.

We do not have automated scheduling feature yet - but you can do this:

Create test execution at Test Collab via API triggered by your Jenkins. Once test execution is assigned, Test Collab will automatically trigger your cucumber tests.

Disclaimer: I'm co-founder of Test Collab.

blocks|key|2086453|text|有两个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2086454|需要管理工具，我们可以将测试与需求相关联并获得报告。您不需要任何其他管理工具来将测试与需求相关联，因为这是使用黄瓜特性文件完成的。对于来自Gherkin的报告，您可以在Jenkins上使用黄瓜-Jenkins插件，在每次测试运行后导出JSON文件中的测试结果，并将Cucumber报告作为执行后的步骤发布。|ordered-list-item|2086455|读取黄瓜功能文件的工具。有一些工具可以读取黄瓜文件，并允许您轻松地从功能文件中在线共享、管理和搜索产品的实时文档。|2086456|示例https://relishapp.com|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|https://relishapp.com/^0|0|0|0|2|L|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|S|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|T|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

There are two questions 

<ol>
<li>Need for management tool where we can associate the tests to the requirements and have the reports. You don't need any other management tools to associate the tests to requirements since that is done using cucumber feature files. For reports from Gherkin, you can use the cucumber-jenkins plugin on Jenkins, export you test results in JSON files after each test run and publish Cucumber reports as a post execution step.</li>
<li>Tools that read the Cucumber feature files. There are tools that read Cucumber files and allow you to easily share, manage and search your product's live documentation online from the feature files.</li>
</ol>

Example <a href="https://relishapp.com" rel="nofollow">https://relishapp.com</a>

blocks|key|252062|text|我同意查克的观点，你真的不应该把你的特征文件存储在任何中医程序中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|252063|但是，如果您正在编写Gherkin格式的验收测试，以及我一直在使用的Testrail自动化的特定测试。它有一个相当好的API和UI脚本(我使用的是在Gherkin关键字上突出显示的脚本)。|252064|然后，我拿出其中的一些，并从我将要自动化的文件中创建特性文件(然后我将继续在我们选择的回购中保留这些文件)。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

I agree with Chuck, really you shouldn't be storing your feature files in any TCM program.

However, if you are writing acceptance tests in Gherkin format and the automating specific ones I've been using Testrail. It has a pretty good API and UI scripts (Im using one that does highlighting on the Gherkin keywords).

I then take some of those and create feature files out of the ones im going to automate (which I will then proceed to keep in our repo of choice).

In my company we have our tests specified in Gherkin (Cucumber), and we use Jenkins to schedule the execution of these tests.

We have the need of a management tool, where we can associate the tests to the requirements and have the reports. Are there some tools that read the Cucumber feature files?

Thanks

What test management tool to manage Cucumber tests?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在我的公司里，我们用Gherkin (黄瓜)指定了我们的测试，我们使用Jenkins来安排这些测试的执行。我们需要一个管理工具，在这个工具中，我们可以将测试与需求联系起来，并拥有报告。是否有读取黄瓜功能文件的工具？谢谢

问管理黄瓜测试的测试管理工具是什么？
EN

回答 7

Stack Exchange QA用户

Stack Exchange QA用户

Stack Exchange QA用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问管理黄瓜测试的测试管理工具是什么？EN

回答 7

Stack Exchange QA用户

Stack Exchange QA用户

Stack Exchange QA用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问管理黄瓜测试的测试管理工具是什么？
EN