Recent changes to Checkers

Checkers modified by Romain Delamare

Romain Delamare — Thu, 18 Apr 2013 15:33:37 -0000

--- v5
+++ v6
@@ -38,4 +38,4 @@
 Writing a checker
 -----------------

-To write a checker, you need to extend `ClassChecker` or `MethodChecker`, depending on the kind of checker you want to create. These are abstract classes, so you need to implement `check`. This method should throw an `EasycoverageAssertionFailedError` if the check fails. The `shouldCheck` has been implemented; if you re-implement it, also call `super.shouldCheck` as it will verify that the subject class or subject method has not been annoted with `SkipAutomaticTests`.
+To write a checker, you need to extend `ClassChecker` or `MethodChecker`, depending on the kind of checker you want to create. These are abstract classes, so you need to implement `check`. This method should throw an `EasycoverageAssertionFailedError` if the check fails. Class checkers (respectively method checkers) also need to implement `shouldCheckClass` (respectively `shouldCheckMethod`).

Checkers modified by Romain Delamare

Romain Delamare — Thu, 18 Apr 2013 10:15:29 -0000

--- v4
+++ v5
@@ -19,7 +19,7 @@
 - `NPEConstructorChecker`
 Checkers that verifies, for every controllers of a class, that they do not have a null pointer exception.
 - `NullValueEqualsChecker`
-Checkers that verifies that `equals` does not return null, for each class implementing it.
+Checkers that verifies that `o.equals(null)` always return false.
 - `ToStringNotNullChecker`
 Checkers that vefiries that `toString` does not return `null`, for each class that implements it.

WikiPage Checkers modified by Romain Delamare

Romain Delamare — Thu, 06 Dec 2012 17:04:12 -0000

--- v3
+++ v4
@@ -10,28 +10,28 @@
 
 ### Class checkers
 
-- BijectiveCompareToChecker
+- `BijectiveCompareToChecker`
 Checkers that verifies that for any class implementing `Comparable`, `o1.compareTo(o2)` is always `-o2.compareTo(o1)`.
-- BijectiveEqualsChecker
+- `BijectiveEqualsChecker`
 Checkers that verifies that, for any class implementing `equals`, `o1.equals(o2)` returns the same result as `o2.equals(o1)`.
-- CloneChecker
+- `CloneChecker`
 Checkers that verifies that, for each class implementing `Cloneable`, that `o.equals(o.clone)`.
-- NPEConstructorChecker
+- `NPEConstructorChecker`
 Checkers that verifies, for every controllers of a class, that they do not have a null pointer exception.
-- NullValueEqualsChecker
+- `NullValueEqualsChecker`
 Checkers that verifies that `equals` does not return null, for each class implementing it.
-- ToStringNotNullChecker
+- `ToStringNotNullChecker`
 Checkers that vefiries that `toString` does not return `null`, for each class that implements it.
 
 ### Method checkers
 
-- ArrayIndexOutOfBoundExceptionChecker
+- `ArrayIndexOutOfBoundExceptionChecker`
 Checkers that verifies that no array index out of bound are thrown. It will try to invoke each method with min and max values.
-- GetterNotNullChecker
+- `GetterNotNullChecker`
 Checkers that checks a getter does not return null.
-- NPEMethodChecker
+- `NPEMethodChecker`
 Checkers that verifies that a method does not throw a null pointer exception.
-- SetterChecker
+- `SetterChecker`
 Checkers that verifies, for a getter/setter pair, that the value return by the getter is the value previously set.

WikiPage Checkers modified by Romain Delamare

Romain Delamare — Thu, 06 Dec 2012 16:40:13 -0000

--- v2
+++ v3
@@ -3,7 +3,7 @@
 
 Checkers perform automatic dynamic verifications. There are two kinds of of checkers: class checkers and method checkers. Class checkers extend `ClassChecker` and are run a class. They usually perform verifications on specific methods in a class, such as `toString`. Method checkers extend `MethodChecker` and are run on each method.
 
-The `IEasycoverageChecker` interface has two methods, `check` and `shouldCheck`. `check` performs the verification, while `shouldCheck` returns true if the checker is applicable on the current class or method. `ShouldCheck` is used to avoid unnecessary calls to `check`.
+The `IEasycoverageChecker` interface has two methods, `check` and `shouldCheck`. `check` performs the verification, while `shouldCheck` returns true if the checker is applicable on the current class or method. `shouldCheck` is used to avoid unnecessary calls to `check`.
 
 Implemented checkers
 --------------------
@@ -33,3 +33,9 @@
 Checkers that verifies that a method does not throw a null pointer exception.
 - SetterChecker
 Checkers that verifies, for a getter/setter pair, that the value return by the getter is the value previously set.
+
+
+Writing a checker
+-----------------
+
+To write a checker, you need to extend `ClassChecker` or `MethodChecker`, depending on the kind of checker you want to create. These are abstract classes, so you need to implement `check`. This method should throw an `EasycoverageAssertionFailedError` if the check fails. The `shouldCheck` has been implemented; if you re-implement it, also call `super.shouldCheck` as it will verify that the subject class or subject method has not been annoted with `SkipAutomaticTests`.

WikiPage Checkers modified by Romain Delamare

Romain Delamare — Thu, 06 Dec 2012 15:25:45 -0000

--- v1
+++ v2
@@ -24,3 +24,12 @@
 Checkers that vefiries that `toString` does not return `null`, for each class that implements it.
 
 ### Method checkers
+
+- ArrayIndexOutOfBoundExceptionChecker
+Checkers that verifies that no array index out of bound are thrown. It will try to invoke each method with min and max values.
+- GetterNotNullChecker
+Checkers that checks a getter does not return null.
+- NPEMethodChecker
+Checkers that verifies that a method does not throw a null pointer exception.
+- SetterChecker
+Checkers that verifies, for a getter/setter pair, that the value return by the getter is the value previously set.

WikiPage Checkers modified by Romain Delamare

Romain Delamare — Thu, 06 Dec 2012 14:37:54 -0000

Checkers ======== Checkers perform automatic dynamic verifications. There are two kinds of of checkers: class checkers and method checkers. Class checkers extend `ClassChecker` and are run a class. They usually perform verifications on specific methods in a class, such as `toString`. Method checkers extend `MethodChecker` and are run on each method. The `IEasycoverageChecker` interface has two methods, `check` and `shouldCheck`. `check` performs the verification, while `shouldCheck` returns true if the checker is applicable on the current class or method. `ShouldCheck` is used to avoid unnecessary calls to `check`. Implemented checkers -------------------- ### Class checkers - BijectiveCompareToChecker Checkers that verifies that for any class implementing `Comparable`, `o1.compareTo(o2)` is always `-o2.compareTo(o1)`. - BijectiveEqualsChecker Checkers that verifies that, for any class implementing `equals`, `o1.equals(o2)` returns the same result as `o2.equals(o1)`. - CloneChecker Checkers that verifies that, for each class implementing `Cloneable`, that `o.equals(o.clone)`. - NPEConstructorChecker Checkers that verifies, for every controllers of a class, that they do not have a null pointer exception. - NullValueEqualsChecker Checkers that verifies that `equals` does not return null, for each class implementing it. - ToStringNotNullChecker Checkers that vefiries that `toString` does not return `null`, for each class that implements it. ### Method checkers