Cruisecontrol.net exec 中的 Fitnesse:测试失败时不要使构建失败

发布于 2024-12-26 06:41:26 字数 613 浏览 1 评论 0原文

我正在尝试将 Fitnesse 与我们的巡航控制设置集成。

我希望在发布功能之前开发一组验收测试。开发我们的验收测试,针对我们的夜间构建运行它们(不是在每次签入时,我们有这方面的工作,但我怀疑我们的验收测试会减慢速度太多)。

因此,我希望能够运行 Fitnesse 测试套件,并且在某些测试失败时不会使其构建失败(期望某些测试会失败,直到我们完成发布)。

我在集成服务器上构建了验收测试,并从命令行运行健身套件(作为集成作业中的执行任务)。

目前,构建失败(当任何测试失败时,runner.exe 具有非零退出代码)。

那么...有人有 fitsharp runner.exe 的退出代码列表吗?有没有办法告诉 Cruisecontrol 执行任务我真的不关心作业的返回值?我应该使用另一个 cc.net 任务吗?

编辑:
目前最好的想法是将 Fitsharp 运行程序包装在批处理文件或 powershell 脚本中,并吞下 Fitness 的返回代码
编辑2:
fitsharp runner.exe 的返回代码是失败的测试数量(使得为 Cruisecontrol.net exec 任务设置成功返回代码元素变得困难)

I'm trying to integrate fitnesse with our cruisecontrol setup.

I'd like to have a set of acceptance tests that we develop before the features for the release are worked on. Develop our acceptance tests, run them against our nightly build (not on every check in, we have a job for that but I suspect our acceptance tests would slow that down too much).

So I want to be able to run the fitnesse test suite and not have it fail the build when some tests fail (the expectation is that some of the tests will fail, until we have finished the release).

I have the acceptance tests building on the integration server and the the fitnesse suite running from the command line (as an exec task in the integration job).

At the moment it is failing the build (runner.exe has a non-zero exit code when any test fails).

So... does anyone have a list of exit codes for fitsharp runner.exe? Is there any way to tell a cruisecontrol exec task that I really don't care about the return value from the job? Is there another cc.net task I should use instead?

Edit:
Current best idea is to wrap the fitsharp runner in a batch file or powershell script and swallow the return code from fitness
Edit2:
Return code from fitsharp runner.exe is the number of tests that failed (making setting the success return codes element for the cruisecontrol.net exec task difficult)

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

萌逼全场 2025-01-02 06:41:26

我认为最好的方法是使用 nant,它与 ccnet 集成得非常好。您可以简单地告诉 nant exec 任务不要使构建失败,请参阅 http: //nant.sourceforge.net/release/latest/help/tasks/exec.html
当您即将发布时,只需将failonerror 属性设置为true 即可。

I think the best way to do it is with nant, which integrates very nicely with ccnet. You can simply tell a nant exec task to not fail the build, see http://nant.sourceforge.net/release/latest/help/tasks/exec.html
When you're close to release, simply set the failonerror property to true.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文