Menu

Tree [r2] /
 History

HTTPS access


File Date Author Commit
 bin 2009-02-11 grandteton [r1] initial check in
 build 2009-02-21 grandteton [r2] add bridge for SDL (Simple Declaration Language)
 dist 2009-02-11 grandteton [r1] initial check in
 lib 2009-02-21 grandteton [r2] add bridge for SDL (Simple Declaration Language)
 src 2009-02-21 grandteton [r2] add bridge for SDL (Simple Declaration Language)
 .classpath 2009-02-21 grandteton [r2] add bridge for SDL (Simple Declaration Language)
 .project 2009-02-11 grandteton [r1] initial check in
 build.xml 2009-02-11 grandteton [r1] initial check in
 readme.txt 2009-02-11 grandteton [r1] initial check in

Read Me

the limitation of jmock/easymock
1. hard to understand
2. hard to reuse


so the goal of SecondMock
1. easy to understand
2. easy to reuse

how to achieve it?
1. contracts between caller and mock are defined in xml file
2. xml file will support testing plan?
3. xml file will support reuse of testing data?
reuseable data should be defined in the data section. and use id for reuse
4. xml file will support reuse of testing logic?
5. implementation of testing logic can be in the xml file directly
6. implementation of testing logic can be defined in the rule engine?
7. implementation of testing plan with state chart?
8. implementation of testing logic should be plugable

what's the api?

1. Given interface  A.java or class  A.java
   A mock = SecondMock.getMock(A.class, xml-file);
   
   
what's defined in xml-file
1. it should define the contract class, which should implement some interface, like
      public interface Contract {
           public Result contract(Condition);  
      }
   
Condition should be the method call (method name , parameter value list...)
Result should be wrapped into java object?
      
      
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.