| @@ -6,6 +6,8 @@ |
|
|
| 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.
|
|
|
| +There is also a new testing package: ))bitUnit((. The bitUnitPackage is an integration of [http://simpletest.sourceforge.net|simpletest] at sourceforge. It was chosen since it was the only package that supports the MVC pattern, which made it possible to integrate with smarty templates. |
| + |
| 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.
|
|
|
| @@ -25,7 +27,7 @@ |
| # All methods within the test class beginning with the letters "test" will be executed by PHPUnit
|
|
|
| So, for our class, this is what the test class would look like:
|
| -{CODE(colors=>php)}<?php
|
| +{CODE source=php}<?php |
| // get the class you're going to test
|
| require_once('MyClass.php');
|
| // always extend the Test class, which is already included from index.php
|
|
|
| @@ -48,7 +50,7 @@ |
| Assert::equalsTrue($this->test->getText() == "some text", 'Value is not set');
|
| }
|
| }
|
| -?>{CODE}
|
| +?>{/CODE} |
| As you can see, its really not too hard. By browsing to the __index.php__ file, each of the Test* files and classes will be initialised and their results presented on the screen.
|
|
|
| The next steps to this test class could be:
|
|
|
| @@ -58,7 +60,7 @@ |
| !The ))PrePostFilter(( tester
|
| A new class was added to the testing framework in
|
| order to test smarty filters. The class can actually test all filters that has the signature
|
| -{CODE(colors=>php)}$output = filtername ($input){CODE}
|
| +{CODE source=php}$output = filtername ($input){/CODE} |
| The class could be modified with more
|
| to handle other kind of input-output test, but
|
| currently only pre- and postfilters are
|
|
|
| @@ -66,7 +68,7 @@ |
|
|
| !!Input Output tester manual
|
| This is a description how to set up tescases for (Smarty)filters.
|
| -The 'TestTikiSmartyFilter.php' is an input - output tester that feeds
|
| +The 'TestBitSmartyFilter.php' is an input - output tester that feeds |
| the contents of a file to the function to be tested (in the first parameter)
|
| and compares what the function returns with another file.
|
|
|
|
|