diff --git a/build.xml b/build.xml index fc1d9fc..1cca85e 100644 --- a/build.xml +++ b/build.xml @@ -1,6 +1,6 @@ - + diff --git a/dist/concordion-extensions-0.1.jar b/dist/concordion-extensions-0.1.jar deleted file mode 100644 index 2121877..0000000 Binary files a/dist/concordion-extensions-0.1.jar and /dev/null differ diff --git a/dist/concordion-extensions-0.2.jar b/dist/concordion-extensions-0.2.jar new file mode 100644 index 0000000..2a76363 Binary files /dev/null and b/dist/concordion-extensions-0.2.jar differ diff --git a/dist/concordion-extensions-0.1.zip b/dist/concordion-extensions-0.2.zip similarity index 90% rename from dist/concordion-extensions-0.1.zip rename to dist/concordion-extensions-0.2.zip index f67cf52..9e9cdfc 100644 Binary files a/dist/concordion-extensions-0.1.zip and b/dist/concordion-extensions-0.2.zip differ diff --git a/dist/specs/image/concordion-logo.png b/dist/specs/image/concordion-logo.png new file mode 100644 index 0000000..35c60de Binary files /dev/null and b/dist/specs/image/concordion-logo.png differ diff --git a/dist/specs/index.html b/dist/specs/index.html new file mode 100644 index 0000000..b10feb3 --- /dev/null +++ b/dist/specs/index.html @@ -0,0 +1,101 @@ + + + + Concordion Specifications + + +

Concordion Specifications

+

+ These pages contain the concordion specifications generated for this + project. Concordion tests are automated acceptance tests which are + written in plain english and linked to the system so they do not go + out-of-date. Find out more at concordion.org. +

+
+

Further Details

+ +
+
Results generated by +Concordion + +
+ + diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/matrix/AssertMatrixEquals.html b/dist/specs/spec/uk/co/codemonkey/concordion/matrix/AssertMatrixEquals.html new file mode 100644 index 0000000..68996e5 --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/matrix/AssertMatrixEquals.html @@ -0,0 +1,194 @@ + + + + assertMatrixEquals + + Matrix processing > + +

assertMatrixEquals

+

+The assertMatrixEquals command evaluates an expression and compares the resulting +Object[][] to the contents of the instrumented table element. The command reports +a success if the evaluation result is equal to the text in the document, or a failure +otherwise. The comparisons are case-sensitive. +

+ +
+

Given an extension with assertMatrixEquals is installed

+

And a test fixture that returns an array of the form [[a,1][b,2]]

+

The following instrumentation

+ 
+   
+   <table myext:assertMatrixEquals="printMatrix()">
+     <tr><td>a</td><td>1</td></tr>
+     <tr><td>b</td><td>2</td></tr>
+   </table>
+  
+
+ +

Should return a successful evaluation result

+
+ +
Results generated by Concordion
in 795 ms on 18-Nov-2011 at 09:38:59 GMT
+ \ No newline at end of file diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/matrix/Matrix.html b/dist/specs/spec/uk/co/codemonkey/concordion/matrix/Matrix.html new file mode 100644 index 0000000..79bf179 --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/matrix/Matrix.html @@ -0,0 +1,192 @@ + + + + Matrix processing + + +

Matrix Processing

+

+ The matrix processing commands allow for easier concordion testing of + functions that work with 2 dimensional matrices. By allowing the use of + html tables to represent the matrix, tests can be defined easily and concisely. +

+ +
+

Further Details

+ +
+
Results generated by +Concordion + +
in 18 ms on 18-Nov-2011 at 09:38:59 GMT
+
+ + diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/matrix/SetMatrix.html b/dist/specs/spec/uk/co/codemonkey/concordion/matrix/SetMatrix.html new file mode 100644 index 0000000..b2f2fa8 --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/matrix/SetMatrix.html @@ -0,0 +1,205 @@ + + + + setMatrix + + Matrix processing > + +

setMatrix

+

+A setMatrix command interprets the instrumented table element as a +two-dimensional Object[][] and sets it to a temporary variable so that +it can be referenced by another command. +

+ +
+

Given an extension with setMatrix is installed

+

The following instrumentation

+ 
+  
+  <table myext:setMatrix="#matrix">
+    <tr><td>a</td><td>1</td></tr>
+    <tr><td>c</td><td>2</td></tr>
+  </table>
+  
+  <span concordion:execute="printMatrix(#matrix)"> print </span> 
+  
+
+ +

Should call the method printMatrix with an array containing the following data

+ + + + + + + + + + +
RowColValue
00a
011
10c
112
+
+ +
Results generated by Concordion
in 321 ms on 18-Nov-2011 at 09:39:00 GMT
+ \ No newline at end of file diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/ChildSpecifications.html b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/ChildSpecifications.html new file mode 100644 index 0000000..0663714 --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/ChildSpecifications.html @@ -0,0 +1,183 @@ + + + What about child specifications without indexes? + + Linking specifications together > +

What about child specifications without indexes?

+

+ Links to child specifications will be added to the nearest available + index. If no index exists for the current directory, a link will be + added to the parent index. +

+ +
+

Given a directory example + with files Example.html + and child/childDetails.html

+

When I run the SpecLinker

+

Then Example.html will contain a link to child/childDetails.html

+
+
Results generated by Concordion
in 403 ms on 18-Nov-2011 at 09:39:00 GMT
+ + \ No newline at end of file diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/DefaultIndex.html b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/DefaultIndex.html new file mode 100644 index 0000000..3622114 --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/DefaultIndex.html @@ -0,0 +1,187 @@ + + + How do I customise the root index page? + + Linking specifications together > +

How do I customise the root index page?

+

+ SpecLinker will automatically create a root index + page for the top level specifications. To use a different file + as the index page, ensure exists at the root of the SpecLinker + classpath as specLinkerDefaultIndex.html. Note: this is + set to become more user friendly in the next release. +

+ + +
Results generated by Concordion
in 73 ms on 18-Nov-2011 at 09:39:01 GMT
+ + \ No newline at end of file diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/LinkLocation.html b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/LinkLocation.html new file mode 100644 index 0000000..e980146 --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/LinkLocation.html @@ -0,0 +1,178 @@ + + + Where will the links be placed on my pages? + + Linking specifications together > +

Where will the links be placed on my pages?

+ +

+ Links will be added to the foot of the page inside a div + with an id of childSpecifications. If SpecLinker + finds a div already exists with this id, the div contents will be removed + and replaced with the generated links. +

+ +
Results generated by Concordion
in 136 ms on 18-Nov-2011 at 09:39:01 GMT
+ + \ No newline at end of file diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/LinkNames.html b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/LinkNames.html new file mode 100644 index 0000000..801a28c --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/LinkNames.html @@ -0,0 +1,188 @@ + + + How are link names determined? + + Linking specifications together > +

How are link names determined?

+

+ When a link is created, the anchor text will be populated with the + title text of the child page. If no title text exists, then the filename + will be used instead. +

+ +
+

Given a child page with title "My Test Title" called MyChild.html

+

When I look at the generated index page

+

Then I will see a link with text "My Test Title"

+
+ +
+

Given a child page called MyChild.html without a title.

+

When I look at the generated index page

+

Then I will see a link with text "MyChild.html"

+
+ +
Results generated by Concordion
in 178 ms on 18-Nov-2011 at 09:39:01 GMT
+ + \ No newline at end of file diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/Running.html b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/Running.html new file mode 100644 index 0000000..2c6f754 --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/Running.html @@ -0,0 +1,223 @@ + + + How do I run the specLinker? + + Linking specifications together > +

How do I run the specLinker?

+ +

+ Generating the links is as simple as running the SpecLinker + main class and passing it two arguments. The first argument + is the directory in which the junit test results are located, + the second is the directory in which the concordion results + are located. +

+ +
+

Ant

+

Simply add a java tag to your concordion test target:

+ 
+      
+    <java classname="uk.co.codemonkey.concordion.specLinker.SpecLinker">
+        <classpath>
+            <path refid="classpath.test"/>
+        </classpath>
+        <arg value="${dir.test.output}"/>
+        <arg value="${dir.concordion.output}"/>
+    </java>
+
+
+ + +
Results generated by Concordion
in 72 ms on 18-Nov-2011 at 09:39:01 GMT
+ \ No newline at end of file diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/SpecLinker.html b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/SpecLinker.html new file mode 100644 index 0000000..fd1c12a --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/SpecLinker.html @@ -0,0 +1,221 @@ + + + + Linking specifications together + + +

Linking specifications together

+

+ Once you have written all your specifications, the question + naturally arises, how do I navigate them? Concordion provides + breadcrumbs which help navigate back up a tree, but relies + on manual links to provide further details. SpecLinker + expands on breadcrumb format to automatically populate index + pages with links to their children, and highlight these links based + on the test results. +

+ +
+

Given a directory example + with files Example.html + and MoreExampleDetails.html +

+

When I run the SpecLinker +

+

Then Example.html will be interpreted as an index + and contain a link to MoreExampleDetails.html +

+
+ + +
Results generated by +Concordion + +
in 117 ms on 18-Nov-2011 at 09:39:02 GMT
+
+ + + diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/resultHighlighting/NestedIndexes.html b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/resultHighlighting/NestedIndexes.html new file mode 100644 index 0000000..ff02293 --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/resultHighlighting/NestedIndexes.html @@ -0,0 +1,186 @@ + + + Are nested indexes highlighted? + + Linking specifications together > Result Highlighting > +

Are nested indexes highlighted?

+

+ When links are highlighted, if any tests below that index + in the tree have failures, the link will be marked as a failure. +

+
+

Given the following file structure:

+ + + + + +
Filename
index.html
child/Child.html
child/failing.html
+

When the specification child/failing.html fails

+

Then the link in the root index will have class: failure

+
+ +
Results generated by Concordion
in 269 ms on 18-Nov-2011 at 09:39:02 GMT
+ + \ No newline at end of file diff --git a/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/resultHighlighting/ResultHighlighting.html b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/resultHighlighting/ResultHighlighting.html new file mode 100644 index 0000000..49b4440 --- /dev/null +++ b/dist/specs/spec/uk/co/codemonkey/concordion/specLinker/resultHighlighting/ResultHighlighting.html @@ -0,0 +1,223 @@ + + + + Result Highlighting + + + +Linking specifications together > +

Result Highlighting

+

+ When the SpecLinker is given the location of the junit concordion + reports, it will set the link class based on the test results. +

+
+

Given the following test results

+

When I look at the generated index page

+

Then I will see a link annotated with class

+ + + + + + + + + + + + + + + + + + + + + + + + + + +
PassesFailsExpected Class
00success
10success
01failure
11failure
+
+ +
+

Further Details

+ +
+
Results generated by +Concordion + +
in 284 ms on 18-Nov-2011 at 09:39:02 GMT
+
+ + +