Unit tests should test interface and only interface

[meg23]

From cyounk...@gmail.com on July 31, 2009 15:46:21

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: http://code.google.com/p/owasp-esapi-java/issues/detail?id=25

[meg23]

From eofte...@gmail.com on September 09, 2009 23:54:21

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.

[meg23]

From manico.james@gmail.com on October 31, 2010 22:57:37

Status: Accepted
Owner: jeff.wil...@owasp.org
Labels: Milestone-Release2.1

[meg23]

From chrisisbeef on November 20, 2010 13:14:10

Blockedon: 168

[meg23]

From chrisisbeef on November 20, 2010 13:14:34

Blockedon: -168 186

[meg23]

From chrisisbeef on November 20, 2010 13:14:55

Owner: chrisisbeef

[meg23]

From chrisisbeef on November 20, 2010 13:15:28

Labels: Component-Other Build-Maven

[kwwall]

Previous comment had blocked on Google Code issue 186. That is now issue #196.