Design Principles

The goal is to test applications on systems which are current with the Open Source state of development, so that their development cycles will incorporate the changes in the underlying operating system. The second goal is to generate useful results that are easily processed/accessibe/shared.

In order to obtain the project goals, BRT must fit in with how people normally test. Our assumption is that people want to test comfortably with minimal modification in their routine. They want immediate feedback. They want to be able to 'tweak' things and run again without fuss if necessary. They also do not want to spend a lot of time setting things up.

Therefore, we are attempting to make BRT-lite more like a flexible tool set than a rigid testing framework. It should have many functions which the user can use all of, or some of. Independent tools should be helpful, not frustrating. It will be good to package the portions seperately in order to allow ease of use of portions without difficulty in installation. Additionally, we want to put extra effort in result presentation, searching and sharing. Unless the results are used for informative reports or for bug-fixes in a timely manner, they are useless.