Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Junit 3.8 <a href="http://www.junit.org/node/363" rel="nofollow">http://www.junit.org/node/363</a> </p> <p>From Dirk Riehle: "JUnit 3.8 Design Documentation Wed, 05/14/2008 - 06:24 — driehle</p> <p>JUnit is increasingly being used in scientific case studies. That's because it is comparatively small, well-known, and self-contained. For anyone who is interested in a detailed design documentation of how JUnit 3.8 works, I have documented its design. I chose JUnit 3.8 because the move to annotations in 4.0 may have made JUnit more convenient to use, but the design less clear (in object-oriented terms). JUnit is not the only common case study, JHotDraw is another. If you have additional case studies with well-documented designs, I'd love to hear about it!"</p> <p>and from <a href="http://dirkriehle.com/2008/04/03/junit-38-documented-using-collaborations/" rel="nofollow">http://dirkriehle.com/2008/04/03/junit-38-documented-using-collaborations/</a></p> <p>"Abstract: This paper describes the design of the unit testing framework JUnit v3.8. The documentation technique employed is an enhanced version of collaboration-based design, also known as role modeling. In collaboration-based design, objects are viewed as playing multiple roles in different contexts, and different contexts are viewed as task specific collaborations. The documentation accounts for every method in the JUnit 3.8 framework by assigning it to a role. It thereby investigates whether roles and collaborations can serve as basic units of functionality provided by a design like a framework. Such a measure of functionality can serve multiple purposes, for example estimating implementation efforts or measuring complexity."</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload