History of TestingSuites
If you don't know about Object Orientation (OO) or 'Black Box' design, take a look at the ObjectOrientation page.
Under the __kernel/test/__ directory, you will find an attempt at our first testing suite. This is supposed to be a quick explanation on how it works.
The testing suite is based on the principles of Object Orientation or 'black box' design. The testing suite only cares about what could possibly go into a class, what if something not meant to go into the class is handled and will the output be the way you like it.
As OO uses a lot of inheritence, by changing something small in a base class, all child classes could be affected and break. Testing suites help prevent this. Also, if developers start putting data into the class, that was never meant for it, testing suites ensure that the class handles them gracefully, rather than die a horrible death.
Lastly, a testing suite also checks that the output is what you expected.
The testing script we use was written by [mailto:vincent@sunlight.tmfweb.nl|Vincent Oostindië], and can be found at
Under the __kernel/test/__ directory, you will find an attempt at our first testing suite. This is supposed to be a quick explanation on how it works.
The testing suite is based on the principles of Object Orientation or 'black box' design. The testing suite only cares about what could possibly go into a class, what if something not meant to go into the class is handled and will the output be the way you like it.
As OO uses a lot of inheritence, by changing something small in a base class, all child classes could be affected and break. Testing suites help prevent this. Also, if developers start putting data into the class, that was never meant for it, testing suites ensure that the class handles them gracefully, rather than die a horrible death.
Lastly, a testing suite also checks that the output is what you expected.
The testing script we use was written by [mailto:vincent@sunlight.tmfweb.nl|Vincent Oostindië], and can be found at