Documentation - Some fixes after review

This commit is contained in:
Jose Luis Osorno
2019-01-16 12:13:02 +01:00
parent 13f6457fbd
commit 2954b72765
2 changed files with 4 additions and 5 deletions

View File

@@ -5,9 +5,9 @@ Last reviewed: 2019-01-16
---
# Integration testing
"Integration testing is the phase in software testing where individual software modules are combined and tested as a group. It occurs after unit testing and
_"Integration testing is the phase in software testing where individual software modules are combined and tested as a group. It occurs after unit testing and
before validation testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined
in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. [Wikipedia]."
in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. [Wikipedia]."_
Even if the definition of integration testing is a general description, the concept is also valid for Alfresco projects.

View File

@@ -121,7 +121,7 @@ classes are included in the folder `integration-tests/src/test/java`.
```
This is specially useful when the ACS endpoint is not exposed at the default location (`http://localhost:8080/alfresco`). This property is important when the
development environment is run using Docker Toolbox (old Windows and MacOS versions). In this case, the container exposed ports are not mapped to localhost,
development environment is run using Docker Toolbox (old Windows and MacOS versions). In this case, the container exposed ports are not mapped to `localhost`,
but to a custom IP provided by the Virtual Box virtual machine (i.e. `http://192.168.99.100:8080/alfresco`).
* The All-In-One project utility scripts (`run.sh` / `run.bat`) offer two different tasks to execute the integration tests:
@@ -131,8 +131,7 @@ but to a custom IP provided by the Virtual Box virtual machine (i.e. `http://192
## Sample tests included in the generated project
The All-In-One archetype includes some basic integration tests that demonstrates the way you can implement the integration tests of your custom module. This
section illustrates what they check.
The All-In-One archetype includes some basic integration tests that demonstrate the way you can implement the integration tests of your custom module.
### `CustomContentModelIT`: Checking the correct existence and setup of a custom model