Introducing Rails into a PHP shop? Or build up what we already use? -

here's setup @ our shop:

• 1 large php app (kohana 2) many dev's , lots of infrastructure
• multiple (4-5 , growing) small php apps 1-2 dev's working on these

issues:

• no testing
• no documentation
• a fragile , tedious deployment process

i'm being moved single large app on side of house multiple smaller apps. lack of testing , proper deployment process in our shop makes me nervous i'll spend more time fixing bugs , deploying fixes writing code new features.

solution a:

• introduce phpunit , selenium
• move on phing , dbdeploy

problem a: setting phpunit has been relatively easy, functional testing selenium has been total pain. our vm's work great dev, selenium pegs needle, plus few simple tests take forever. don't doubt of these technologies playing together, seems mess , complexity of these working seems fragile.

solution b:

• switch rails
• use integrated testing and/or rspec/cucumber (integration of latter seems simple)
• use integrated db migrations
• use capistrano deployments

based on major issues of testing, began rails. based on nature of these other sites manage, think rails may solution. built-in testing, great community, lots of great tools, , fast development.

problem b: every app have right on kohana 2 (php framework) , no 1 in organization knows rails. downside introducing new technology fracturing teams. if migrate sites rails, hit bus, we're kind of screwed.

bottom line:

based on our pain points (deployments, testing, documentation, db migrations), worth cost switch rails? or should stay put in kohana , continue try , other tools built?

any suggestions? gone through similar? management has told me they're open hearing rails , want use best tool possible -- whatever is. our lead architect, however, need convincing if decide switch frameworks on our smaller projects.

there lot of factors influence decision.

if switch rails, keep in mind take while , team learn framework/language , can slow adding features while. depends on team, time constraints , many other factors.

maybe try 1 of small projects rails , see if , team rails (i dont).

the answer different every team. have group meeting , discuss pros , cons of both decisions. have vote.