Date: 2005-01-28T09:59:08 Editor: ZacharySmith Wiki: Apache Beehive Wiki Page: Controls/TestingControls/Milton URL: http://wiki.apache.org/beehive/Controls/TestingControls/Milton
no comment Change Log: ------------------------------------------------------------------------------ @@ -7,9 +7,15 @@ = The Basics = -The main idea behind Milton is to make it easier and faster to write end-to-end tests for the Beehive Controls framework. We want to be able to verify that all features Controls work in the two Control client contexts in Beehive: Java Page Flows (JPF) and the JSR-181 implementation of Java Web Services (JWS). "Note: Jave Web Services in Beehive are called WebServices Metadata (WSM) but use the .jws file extension." To accomplish this we have broken the tests into four pieces. +The main idea behind Milton is to make it easier and faster to write end-to-end tests for the Beehive Controls framework. We want to be able to verify that all features Controls work in the two Control client contexts in Beehive: Java Page Flows (JPF) and the JSR-181 implementation of Java Web Services (JWS). "Note: Jave Web Services in Beehive are called Web Services Metadata (WSM) but use the .jws file extension." To accomplish this we have broken the tests into four pieces. * 1. The Control being used for testing. * 2. A POJO called a Driver which contains the logic which excercises the control and dertermins PASS/FAIL/ABORT * 3. A Client of the control (JPF, JWS, Java) * 4. A JUnit file which is used to access and trigger the client test methods. + +A Controls test using Milton will run in the following order. + + * a. User invokes JUnit Accessor method using either [wiki:/TCH TCH] or standard JUnit runner. + * b. Test method in the JUnit Accessor sends request to corresponding test method on Controls client (JPF, JWS, Java) + * c. The Client instantiates an instance of the test Control and an instance of the Driver. The newly instantiated Control is passed to the corresponding test method on the Driver and a Report is returned. The Report is passed back to the Client and the back to the Accessor where the result in recorded.
