How is the source code (of CMS) being tested?

[Woudloper]

Last weekend I was triggered by one of the forum posters about testing 'CMS Made Simple'. I know that it is not my concern, but something the developers need to deal with. But I wanted to ask something about it and would like to know how you all are testing the PHP code that is being written for 'CMS Made Simple'.

The question I am asking is somehow related the the V-Model. I assume most of you know the V-Model, see:

As mentioned in that model within a project you start with the requirements, create functional/technical/program specification and the actual code. When this all is finished the code is firstly being tested by the 'unit testing' principle (and so on).

The thing I am wondering about. Are you planning to create unit tests for the code that has been written for 'CMS Made Simple' to show that the code has been written meets the 'program specification' (if there are any).

Some background information:

• phpPattern() - Unit Testing in PHP
• PEAR :: Manual for the module/package PHPUnit (PHPUnit)
• Last Craft - Simple Test !!!

I have looked at the above 'unit testing' tools and must say that 'Simple Test' is a very good tool and almost the only one on which development is going on (furthermore it is a good thing imho that it is also a sourgeforge project.

[Ted]

To be perfectly honest, it's not officially tested.  We put out betas and the community tests them...

Now, i'm not saying that it's the best way, but it works for this version of the code.  Now, when we start the rewrite, it will at least be OOP enough that we can unit test the classes and their interaction with the databse.  Wether or not we do that for the frontend as well is still a question.

These are great links, and i'll definitely be checking them out in my research travels.

Thanks!