Black box testing

A couple of modules exist to aid the Drupal developer in creating functionally correct and robust code. Specifically for testing two types exist : there are the white box testing modules such as simple-test and the black box testing modules such as selenium.
For both types the automation principle applies: it is immaterial whether the test under consideration is duplicated or not, since the cost of conducting the test is negligible compared to manual testing. The cost of testing is in maintaining and coordinating the test sets. I would like to propose to initiate a Selenium test repository containing tests that are run by developers against a module, the core or even an entire installation at will.

When it comes to creating a black box testing repository for Drupal, the following principles come to mind:

• Testers construct their own tests which may be submitted to a public repository.
• By mixing tests from the repository a specific test set can be constructed.
• Each test in the repository has a status, which indicates whether it is included in a test set or not.
• A test can be associated with a reported bug or issue.
• Tests in the repository are versioned such that any version can be pulled up at a click's notice . Moreover, tests pertain to a module or core version.
• Test sets are run from the browser, and the results are reported online.

The ultimate purpose is to create a hardened CMS. Your thoughts and views, including those regarding the whole idea, are welcome.