File tree Expand file tree Collapse file tree 1 file changed +11
-0
lines changed
Expand file tree Collapse file tree 1 file changed +11
-0
lines changed Original file line number Diff line number Diff line change @@ -50,6 +50,17 @@ In order to create a containerized AEM integration test image...
5050
5151Once the container is built, configure the project as [ outlined above] ( #containerized-aem-image-via-testcontainers ) and run the tests.
5252
53+ ### Choosing Local Instance vs Containerized Instance vs Remote Instance
54+
55+ Using a local AEM instance is convenient when developing the server-side libraries (` fluentforms.core ` and ` rest-services.server ` )
56+ because deployment of new libraries is easy (just copy the new ` .jar ` files into the local AEM instance's install directory.
57+
58+ Using a containerized AEM instance is convenient for testing new versions of AEM as the installation and configuration of AEM
59+ is automated by the docker instance creation.
60+
61+ Using Remote AEM instances is useful when you have an existing AEM instance running on a remote server that you wish to test
62+ in order to make sure AEM is installed, configured, and functioning correctly.
63+
5364## Testing New Releases of AEM
5465
5566Each time a new version of AEM is released, the integration tests in this project should be run against it.
You can’t perform that action at this time.
0 commit comments