Unit tests should test interface and only interface

[GoogleCodeExporter]

The unit tests packaged with ESAPI should only test the interface and not
contain code that is specific to the default implementations. This means
two things in particular:

1. All types should be from the API interfaces
2. Methods called on instances being tested should only reflect those in
the API

Specific tests that call methods not in the API:
* AuthenticatorTest.testSaveUsers

... more to come.

Original issue reported on code.google.com by cyounk...@gmail.com on 31 Jul 2009 at 7:46

• Blocked on: Split ESAPI into Components  #186

[GoogleCodeExporter]

Maybe split the tests in two. One folder for interface and one for default
implementations. That way you can still test the default implementations on a 
finer
granularity.

Original comment by eofte...@gmail.com on 10 Sep 2009 at 6:54

[GoogleCodeExporter]

Original comment by manico.james@gmail.com on 1 Nov 2010 at 5:57

• Changed state: Accepted
• Added labels: Milestone-Release2.1

[GoogleCodeExporter]

Original comment by chrisisbeef on 20 Nov 2010 at 9:14

[GoogleCodeExporter]

Original comment by chrisisbeef on 20 Nov 2010 at 9:14

[GoogleCodeExporter]

Original comment by chrisisbeef on 20 Nov 2010 at 9:14

[GoogleCodeExporter]

Original comment by chrisisbeef on 20 Nov 2010 at 9:15

• Added labels: Build-Maven, Component-Other