inteligr8/alfresco-sdk
1
0
Fork 0
mirror of https://github.com/Alfresco/alfresco-sdk.git synced 2025-07-31 17:39:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

SDK 4.2 (#609)

Browse Source 
* migration to ACS and Share 7

* updated documentation to refer to version 4.2

* Migrated to Travis

* Dynamic Keystore settings + APL2 License fix

* Enterprise images pulled from quay.io

Co-authored-by: gfertuso <giovanni.fertuso@alfresco.com>
This commit is contained in:
Andrea Ligios
2021-02-09 13:18:12 +01:00
committed by GitHub
parent 7f19645f20
commit bf853d72c8
44 changed files with 314 additions and 217 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/advanced-topics/integration-testing/README.md
View File

@@ -1,7 +1,7 @@
---
Title: Integration testing
Added: v3.0.0
Last reviewed: 2019-10-18
Last reviewed: 2021-02-09
---
# Integration testing
@@ -11,11 +11,11 @@ in an integration test plan to those aggregates, and delivers as its output the
Even if the definition of integration testing is a general description, the concept is also valid for Alfresco projects.
The Alfresco SDK 4.1 keeps the same general idea of integration testing provided by SDK 3.0, but this new version reshapes it slightly to leverage on a
The Alfresco SDK 4.2 keeps the same general idea of integration testing provided by SDK 3.0, but this new version reshapes it slightly to leverage on a
Docker-oriented environment.
Here are the basics to understanding and using integration testing in the context of projects created with the SDK, from a technical perspective:
* SDK 4.1 develops integration tests for the platform only. Currently, the integration tests that the SDK is able to manage by default is related to
* SDK 4.2 develops integration tests for the platform only. Currently, the integration tests that the SDK is able to manage by default is related to
Alfresco Content Services (ACS) only.
* Integration tests require an ACS instance to be up and running. You will see that all the scripts and commands are designed to easily manage this
requirement, but the prerequisite for the SDK is that an ACS instance is available.

4
docs/advanced-topics/integration-testing/it-running.md
View File

@@ -1,11 +1,11 @@
---
Title: How to run SDK's integration tests
Added: v3.0.0
Last reviewed: 2019-10-18
Last reviewed: 2021-02-09
---
# How to run SDK's integration tests
Running the integration tests of a project generated from the Alfresco SDK 4.1 archetypes is pretty easy. Let's distinguish different cases of executing the
Running the integration tests of a project generated from the Alfresco SDK 4.2 archetypes is pretty easy. Let's distinguish different cases of executing the
integration tests.
## Command line

2
docs/advanced-topics/integration-testing/it-working.md
View File

@@ -36,7 +36,7 @@ or set the Java system property `acs.endpoint.path`.
## Integration tests configuration in the All-In-One project
So, taking into account the previous section, let's see how the integration tests are configured in a project generated from the SDK 4.1 All-In-One archetype.
So, taking into account the previous section, let's see how the integration tests are configured in a project generated from the SDK 4.2 All-In-One archetype.
* The maven dependencies required to execute the integration tests are deployed to the ACS Docker image in the `PROJECT_ARTEFACTID-platform-docker` maven
module using the `maven-dependency-plugin`. The configuration is done in the file `PROJECT_ARTEFACTID-platform-docker/pom.xml`: