gma / nesta

File Based CMS and Static Site Generator
http://nestacms.com
MIT License
902 stars 122 forks source link

Migrate tests to test/unit #32

Closed gma closed 8 years ago

gma commented 13 years ago

I much prefer minitest to Rspec, primarily because upgrading to the latest Rspec API isn't something I'm prepared to spend my free time doing.

We also need to split unit tests from integration tests, and separate the integration tests into those that can be expected to pass for any theme, and those that are specific to the default theme.

Tasks

After merging branch to master:

jcoffin commented 13 years ago

For what its worth, you've got my vote for minitest. I would happily help. This is a bit tangential, but it might also be a good idea to move some of the tests to separate files; 500+ lines of nested describe blocks get confusing.

gma commented 13 years ago

On 15 Apr 2011, at 19:43, jcoffin wrote:

For what its worth, you've got my vote for minitest. I would happily help. This is a bit tangential, but it might also be a good idea to move some of the tests to separate files; 500+ lines of nested describe blocks get confusing.

I agree; it's getting too unwieldy as it stands. The time to decide what to do there is after the theme specific tests have been split out into a separate folder.

I need to get it started at some point, and I'm keen to do that before any more really significant features go in. I also want to improve the API of the factory methods as part of this refactoring; they've gotten into a bit of a mess.

Thanks for the offer of help. I'll get in touch when the time comes if it's takes me more than a few hours to port them over.