Page History
...
- Testing of activation that activates content and checks for results
- Crawling test that requests all the pages and checks for rendering exceptions
- Log crawling test that reads logs and checks for rendering exceptions.
Concurrent builds for bundles on Jenkins
Integration tests run concurrently on Jenkins for CE and EE bundles, and for our various branches (5.0.x up to master). Therefore each branch/bundle must use its own ports for starting up Jetty and e.g. sending shutdown signals through the Cargo wrapper.
Here are the ports in use for our current builds:
| CE bundle | EE bundle | ||||||
| containerHttpPort | cargoRmiPort | cargoTomcatAjpPort | containerHttpPort | cargoRmiPort | cargoTomcatAjpPort | ||
| bundle-4.5.x | 8067 | 8066 | 9067 | 9066 | |||
| bundle-5.0.x | 8077 | 8076 | - | - | |||
| bundle-5.1.x | 8099 | 8098 | 9099 | 9098 | |||
| bundle-5.2.x | 8199 | 8198 | 9199 | 9198 | |||
| bundle-5.3.x | 8299 | 8298 | 9299 | 9298 | |||
| bundle-5.4.x | 8399 | 8398 | 8397 | 9399 | 9398 | 9397 | |
| bundle-master (5.5).x | 8499 | 8498 | 8497 | 9499 | 9498 | 9497 | |
| bundle-master (5.5) | 8599 | 8598 | 8597 | 9599 | 9598 | 9597 | |
| teams/platform | 7529 | 7528 | - | - | |||
| teams/cms | 8267 | 8266 | 9267 | 9266 | |||
| teams/integration | 8468 | 8467 | 9468 | 9467 | |||
| bundle-debug | 6667 | 6666 | 6665 | 7771 | 7772 | 7773 | |
| bundle-5.4.x-cp13n | - | - | 9390 | 9389 | 9388 | ||
Configuration for these ports is located in:
...
When branching a bundle's master to the next major version, one should update these ports according to the pattern in the table above.
Debugging
To debug these tests, one way to go is to start the container the same way as for the manual tests, with mvn clean verify -Pmanual-tests, and run the tests from the IDE in debug mode.
Somehow, memory issues seem to arise, at least with EE, in the manual-tests mode. This seemed to have helped, not sure which statement exactly:
...
Overview
Content Tools