Rename Mage-Test Framework (or at least, remove the hyphen)

[ajbonner]

With 'MageTest/MageSpec' and 'MageTest/BehatMage', the name 'MageTest/Mage-Test' seems a little out of place. The hypen is redundant, and at least for consistency, I think that should go. I would go further though. Given each of the other frameworks refer to the testing library they build upon, rather than MageTest/Mage-Test, shouldn't there be a MageTest/MageUnit?

That way the name 'MageTest' can refer to the overall family of frameworks, and the individual frameworks themselves identify directly the tools, whether behat, phpspec, or phpunit, that they wrap around.

[alistairstead]

👍 I would support this but have not done this previously for fear of breaking backwards compatibility compatibility. However with the fresh investment of time in the projects this seems appropriate.

[ajbonner]

I guess the cleanest solution in the short-term is to just start a new repository with a copy of the develop branch under the new name. Leave Mage-Test as is, with an updated README screaming that the project has moved and is no longer actively maintained.

[alistairstead]

I don't think many people are using the project via git so I'm happy to just rename the repos.

On 5 Jun 2013, at 22:32, Aaron Bonner notifications@github.com wrote:

I guess the cleanest solution in the short-term is to just start a new repository with a copy of the develop branch under the new name. Leave Mage-Test as is, with an updated README screaming that the project has moved and is no longer actively maintained.

—
Reply to this email directly or view it on GitHub.

[punkstar]

Github supports redirects of browsers when changing the name of the repository (https://github.com/blog/1508-repository-redirects-are-here), and existing clone repos are claimed to work too!