这是我的目标：
1. 在 Eclipse 中运行我的测试，然后看到漂亮的绿色或红色条。
2. 使用构建工具在命令行上运行我的测试。
我倾向于规范和 sbt，但我无法让它们工作。我不想拿起 Maven。我的问题是以下哪一组效果最好？
- sbt 和 scalatest
- sbt 和规格
- ant 和 scalatest
- ant 和规格
- 还有其他东西吗？
需要考虑的是其他人需要付出多少努力才能使项目在新机器上启动并运行。如果它能与 Hudson 集成，那就加分了。
Here are my goals:
1. Run my tests in Eclipse and see the pretty green or red bar.
2. Run my tests on the command line with a build tool.
I'm leaning towards specs and sbt, but I can't get them to work. I have no desire to pick up Maven. My question is which one of the follow sets works best?
- sbt and scalatest
- sbt and specs
- ant and scalatest
- ant and specs
- something else?
A consideration is how much effort do other people need to get the project up and running on a new machine. Bonus points if it can integrate with Hudson.
发布评论
评论（2）
SBT绝对是超越ant的方法。 Ant 不会为您提供与 Maven 项目结构的一致性，并且会迫使您推出自己的依赖项管理。
scalatest 或specs 都可以工作。前者似乎是事实，但我在规格上得到了很好的结果。
我不是 Eclipse 用户，但如果其中一个测试库不受支持，我会感到惊讶。
SBT is definitely the way to go over ant. Ant will not give you congruency with maven project structures and would force you to roll your own dependency management.
Either scalatest or specs will work. The former seems to be a de facto, but I get excellent results with specs.
I am not an Eclipse user, but would be surprised if either test library was not supported.
我目前正在将规范项目切换到 sbt 并与 Mark Harrah 一起修复一些问题（查看 sbt 邮件列表 了解详细信息）。
请发布您在规格和 sbt 方面可能遇到的任何问题，我会尽力尽快修复它们。
谢谢，
埃里克。
I'm currently switching the specs project to sbt and fixing a few things with Mark Harrah (check out the sbt mailing list for the details).
Please post any issues you may have with specs and sbt and I'll try to fix them ASAP.
Thanks,
Eric.