如果您使用单元测试框架进行功能测试，您还可以将它们作为夜间构建的一部分运行，并使用 CI 服务器（Hudson 或 Cruise Control 或...）安排它
First of all, our developers are not allowed to check in code without running the unit tests. We also run a CI server (Hudson), which builds after a commit and runs the unit tests. We are working on getting the functional tests implemented for the nightly builds.
You said your developers test the software? This is a bad thing. At least let a developer that is not familiar with the code to test your app otherwise you are likely to overlook some bugs, because their existence was ruled out by the developer writing the code. Additionally, who writes the functional tests? Developers again? You should get your BA's to write them. Always remember, four eyes see more than two.
So after all that said, I assume, that the unit tests, will always be run before code is checked into your SCM. The following is targeted primarily at the functional tests.
Simple solution:
You can always create scripts to bundle your tests (batch or shell script that runs the individual test).
Executing of test suites is actually one of the purposes of Hudson
Collecting and presenting results, that is what Hudson is for
See above, can be done with Hudson, without abusing it.
A good solution:
Did you look at tools like IBM Rational Quality Manager? Depending on the test tools you use, you might want to use a test management tool different one. Oracle also offers a tool for it. Don't be mistaken usually these tools can be fairly expensive and offer way more than you want to use. With a little bit help from google you should find something that suits your needs. My keywords were "centralized test management".
In case you use FitNesse for your functional test. You can define suites in FitNesse and I think a suite can be part of a larger suite. FitNesse definitely keeps historic test data. The test can be run from command line which enables you to run the tests from ant or maven.
If you use a unit test framework for your functional testing you can also run them as part of an nightly build and schedule it using your CI server (Hudson or Cruise Control or ...)
发布评论
评论（1）
首先，我们的开发人员不允许在不运行单元测试的情况下签入代码。我们还运行一个 CI 服务器 (Hudson)，它在提交后构建并运行单元测试。我们正在努力为夜间构建实施功能测试。
您说您的开发人员测试了该软件？这是一件坏事。至少让不熟悉代码的开发人员来测试您的应用程序，否则您可能会忽略一些错误，因为编写代码的开发人员排除了它们的存在。此外，谁编写功能测试？又是开发商？你应该让你的学士学位来写它们。永远记住，四只眼睛比两只眼睛看得更清楚。
综上所述，我认为单元测试始终会在代码签入 SCM 之前运行。以下主要针对功能测试。
简单的解决方案：
一个好的解决方案：
您是否查看过像 IBM Rational Quality Manager 这样的工具？根据您使用的测试工具，您可能需要使用不同的测试管理工具。 Oracle 还为此提供了一个工具。不要误会，通常这些工具可能相当昂贵，并且提供的功能远远超出您想要使用的功能。在谷歌的帮助下，您应该可以找到适合您需求的东西。我的关键词是“集中测试管理”。
如果您使用 FitNesse 进行功能测试。您可以在 FitNesse 中定义套件，我认为套件可以是更大套件的一部分。 FitNesse 绝对会保留历史测试数据。可以从命令行运行测试，这使您能够从 ant 或 maven 运行测试。
如果您使用单元测试框架进行功能测试，您还可以将它们作为夜间构建的一部分运行，并使用 CI 服务器（Hudson 或 Cruise Control 或...）安排它
First of all, our developers are not allowed to check in code without running the unit tests. We also run a CI server (Hudson), which builds after a commit and runs the unit tests. We are working on getting the functional tests implemented for the nightly builds.
You said your developers test the software? This is a bad thing. At least let a developer that is not familiar with the code to test your app otherwise you are likely to overlook some bugs, because their existence was ruled out by the developer writing the code. Additionally, who writes the functional tests? Developers again? You should get your BA's to write them. Always remember, four eyes see more than two.
So after all that said, I assume, that the unit tests, will always be run before code is checked into your SCM. The following is targeted primarily at the functional tests.
Simple solution:
A good solution:
Did you look at tools like IBM Rational Quality Manager? Depending on the test tools you use, you might want to use a test management tool different one. Oracle also offers a tool for it. Don't be mistaken usually these tools can be fairly expensive and offer way more than you want to use. With a little bit help from google you should find something that suits your needs. My keywords were "centralized test management".
In case you use FitNesse for your functional test. You can define suites in FitNesse and I think a suite can be part of a larger suite. FitNesse definitely keeps historic test data. The test can be run from command line which enables you to run the tests from ant or maven.
If you use a unit test framework for your functional testing you can also run them as part of an nightly build and schedule it using your CI server (Hudson or Cruise Control or ...)