Thanks, Mike. I already gave it a look when I saw you were plugging phpunit in QCodo, and just reread it right now.
I just can't figure out how usefull test-systems are when the result comes out of a complex combination (the application is role-based, users can have multiple roles which add together to give them rights on the application, and of course there are exceptions and exceptions to exceptions), this result being rendered on a display (for instance, the “Edit” button will appear or won't, according to user's roles). And the permissions also come out of the workflow and the “document's status”. So I'd say we have 20 users with different roles and rights, and 20 different “documents” to test for 10 possible actions - not exactly 4000 combinations, but tens of them for sure.
So apart login in with each user profile, and test if he gets this or that button in each of the tens of document's combinations... I can't see how this can be described or enumerated - which I think has to be done before testing begins.
I apologize because this question is beyond strictly QCodo - but I'd appreciate if one of you guys could show me where I'm missing the point.