You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16-3Lines changed: 16 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,11 +28,9 @@ Following tools are required to run the test suite
28
28
- recommended version is 22.
29
29
-[Node Version Manager (nvm)](https://github.com/nvm-sh/nvm) is recommended optional tool to install & manage multiple Node environments
30
30
-[npx](https://github.com/npm/npx) CLI tool used to exeute binaries from project's `node_modules` directly (instead of providing absolute/relative path to the commannds). It is used in multiple build steps.
31
-
-[Podman](https://podman.io) | [Docker](https://www.docker.com) as a container runtime used by TestContainers. Note that when using Podman as container runtime you may need to export following environment variables and start podman socket:
31
+
-[Podman](https://podman.io) | [Docker](https://www.docker.com) as a container runtime used by TestContainers. Podman is auto-detected: `DOCKER_HOST`, `TESTCONTAINERS_RYUK_DISABLED`, and `podman.socket` are configured automatically. To override, set the environment variables manually before running the test suite:
- the path can be found by command `podman info --debug` and look for `path` in `remoteSocket` section.
35
-
-`systemctl --user start podman.socket`
36
34
- Java. Yes we'll need Java to write deployments/applications that will be deployed onto the running WildFly container.
37
35
-[Maven](https://maven.apache.org). Yes, we'll need Maven to ease up the development of the deployed applications & downloading needed JDBC drivers for datasource & drivers UI tests. Maven is mostly used embedded by [node-maven](https://github.com/headcr4sh/node-maven) JS wrapper to execute Maven & Java related tasks into the build automation.
38
36
@@ -96,6 +94,21 @@ Following is a table of supported environment properties that can be used when r
96
94
|`MYSQL_IMAGE`|`docker.io/library/mysql:latest`| MySQL image to be used for datasource tests |
97
95
|`MARIADB_IMAGE`|`docker.io/library/mariadb:latest`| MariaDB image to be used for datasource tests |
98
96
|`MSSQL_IMAGE`|`mcr.microsoft.com/mssql/server:2022-latest`| Microsoft SQL Server image to be used for datasource tests |
JDBC driver jars are used in datasource tests. They are downloaded automatically by Maven during `npm install` (via `npm run resources`) and placed into `packages/testsuite/cypress/fixtures/jdbc-drivers/`. These jars are `.gitignore`d and built fresh each time.
102
+
103
+
### Where versions are defined
104
+
105
+
Driver versions are managed in [`packages/resources/pom.xml`](packages/resources/pom.xml) under `<dependencyManagement>`. The download is configured in [`packages/resources/modules/jdbc-drivers/pom.xml`](packages/resources/modules/jdbc-drivers/pom.xml).
106
+
107
+
### How to update
108
+
109
+
1. Update the version in `packages/resources/pom.xml` under `<dependencyManagement>`
110
+
2. Run `npm install` or `npm run resources` to download the new jars
111
+
3. No test spec changes needed -- driver paths are resolved automatically at runtime by the `resolve:jdbc:driver` Cypress task using the artifact prefix (e.g., `postgresql`, `mysql-connector-j`)
0 commit comments