Permalink
Browse files

Removing information about integration testing from `Unit` docblock.

There is now an `Integration` class.
  • Loading branch information...
1 parent 5a10e14 commit 5e0f6137e43ba4ee0274890da9dadea2efd0e594 @davidpersson davidpersson committed May 20, 2012
Showing with 4 additions and 11 deletions.
  1. +0 −1 test/Integration.php
  2. +4 −10 test/Unit.php
View
@@ -17,7 +17,6 @@
* with. Example: the `Session` class and the `Php` adapter. Unit tests will ensure that
* both the `Session` and `Php` classes behave correctly under isolation, while an integration
* test ensures that the two classes interact and interface correctly.
- *
*/
class Integration extends \lithium\test\Unit {
View
@@ -22,21 +22,15 @@
* assertion is correct, the test passes, otherwise it fails. Most assertions take an expected
* result, a received result, and a message (to describe the failure) as parameters.
*
+ * Unit tests are used to check a small unit of functionality, such as if a
+ * method returns an expected result for a known input, or whether an adapter
+ * can successfully open a connection.
+ *
* Available assertions are (see `assert<assertion-name>` methods for details): Equal, False,
* Identical, NoPattern, NotEqual, Null, Pattern, Tags, True.
*
* If an assertion is expected to produce an exception, the `expectException` method should be
* called before it.
- *
- * Both _case_ (unit) and _integration_ tests extend this class. These two test types can loosely
- * be defined as follows:
- * - Case: These tests are used to check a small unit of functionality, such as if a method
- * returns an expected result for a known input, or whether an adapter can successfully open a
- * connection.
- * - Integration: These are tests for determining that different parts of the framework will work
- * together (integrate) as expected. For example, a model has CRUD functionality with its
- * underlying data source.
- *
*/
class Unit extends \lithium\core\Object {

0 comments on commit 5e0f613

Please sign in to comment.