Build spring cleaning
Reported by Brian Takita | January 16th, 2008 @ 10:35 AM
The current build is slow and fragile. It is also very difficult to diagnose issues.
One step that would be useful is to move as much as possible into separate suites and spec helpers. Move as much as possible out of the pre_commit scripts and into individual specs or spec helpers.
For example, the rspec on rails generators can be tested by shelling out inside of a spec, instead of inside of pre_commit.
Comments and changes to this ticket
-
David Chelimsky January 16th, 2008 @ 02:50 PM
- → State changed from “new” to “open”
Great idea, though this should probably be broken out into separate tickets. I have a couple of other ideas that I'll do that with. Brian, can you break this one up as well? Let's tag everything to build.
-
Brian Takita May 25th, 2008 @ 09:28 PM
- → State changed from “open” to “duplicate”
Individual tickets are being created.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Behaviour Driven Development for Ruby.
