Added Testing Strategy documentation

Author: SebastianWendorf

docs/development/Testing Strategy.md

@@ -0,0 +1,12 @@
+# Testing Strategy
+-> currently the LCE and jQA Plugin are tested separately via suites of integration tests
+
+**LCE Integration Tests:**
+- located under `./typescript/test`
+- they test the extraction of individual [[Concepts|concepts]] by running the complete extraction process on different sample projects and validating the resulting `LCEConcept` objects
+- to simply the test code a number of utility methods are defined under `./typescript/test/utils`
+
+**jQA Plugin Integration Tests:**
+- located under `./java/src/test`
+- they test the generation of graph structures based on sample JSON reports generated by the LCE
+- for changes in the report data structures the sample reports have to be re-generated by running `./java/src/test/resources/regenerate-test-data.sh`

docs/index.md

@@ -46,7 +46,7 @@ The tool currently only supports projects using ECMAScript modules.
 This plugin is based on the [LCE Architecture](https://jqassistant-plugin.github.io/jqassistant-lce-docs/).
 - [[Codebase Layout]]
 - [[Extensions]]
-- *TODO: Testing Strategy*
+- [[Testing Strategy]]
 
 **Base LCE Architecture Implementation:**
 - [[Concepts]]

docs/usage/Node Relation - Dependencies.md

@@ -74,6 +74,7 @@ export class B {
 	- the property `prop` is used once by the method `run` in its assignment statement
 
 The following propagations/aggregations take place:
+
 2. Target propagation:
 	- the direct dependency to the method is propagated upwards to the class level where it is combined with the existing direct dependency to the class (leading to a combined cardinality of `2`)
 	- the dependency to the class (with the aggregated cardinality of `2`) is propagated up once more to the module level