Re: testcase repository

> 2. This idea works well for the 'built in' parts of PHP (i.e. testing > 'foreach' statement, or reading files etc) but is not practical for > testing the modules, as it will need the correct module installation, > and MySQL installation on any testing computer. Not an insurmountable > problem, but needs thinking about. A given regression test could include URL of a static copy of correct output, as well as the people willing to test a script on the various platforms/software/versions. Or should that be independent of a particular test script, and only rely on platform/software/version, and have a pool of testers who would be fed the script to test and the expected output... Or even would already, as testers, have the testing/comparing shell... Of course, some regression tests may not be able to have predictable output, so a certain amount of flexibility will have to be allowed for -- Perhaps some sort of notes field for any given test and the expected output is needed. Also any setup that can't be scripted easily, such as database or table creation, which may or may not be a good idea to have allowed to your PHP web-server user on a testing machine...