I think the best way to choose is narrowing it down to a few potential frameworks/stacks that you (and your team, if applicable) thinks would be the best fit fo

I think the best way to choose is narrowing it down to a few potential frameworks/stacks that you (and your team, if applicable) thinks would be the best fit for your project. I don't believe any of these frameworks are the one answer to all your problems. At work we build an enterprise level government used application in CakePHP. It's done fairly well, but given the ability to migrate our platform I would jump at the chance. We begun trying to practice TDD on the project and it's been nothing but a nightmare! Whether it's Simpletest or CakePHP's implementation of Simpletest we haven't figured out (or had the time to dive in and figure it out). We run into issue after issue. The littlest change to the way our app runs at the core seems to trigger a shit storm of little issues here and there. Granted, a lot of this has to do with the architecture that was put in place by the Sr. developer before I got here, but it's definitely becoming an issue... Might also be worth noting that CakePHP is a (poor in my opinion) port of Rails to PHP.