Directories
¶
| Path | Synopsis |
|---|---|
|
nativeapp
Package nativeapp reproduces the legacy DIA component tool's golang app launcher (app-launchers/golang.bash, no docker image): it starts the project binaries built into $GOPATH/bin as detached native processes, each on an incrementing port with the emulator host env vars, and stops them by name.
|
Package nativeapp reproduces the legacy DIA component tool's golang app launcher (app-launchers/golang.bash, no docker image): it starts the project binaries built into $GOPATH/bin as detached native processes, each on an incrementing port with the emulator host env vars, and stops them by name. |
|
stablemocks
Package stablemocks launches the third-party mocks for the component pipeline using the official public images for each tool, with a fixed docker run contract (network, ports, mounts, container names and readiness) so `gtool services up --stable` provides a reproducible mock environment that seeds data from test/component/mocks-data.
|
Package stablemocks launches the third-party mocks for the component pipeline using the official public images for each tool, with a fixed docker run contract (network, ports, mounts, container names and readiness) so `gtool services up --stable` provides a reproducible mock environment that seeds data from test/component/mocks-data. |
|
stablekarate
Package stablekarate reproduces the legacy DIA component tool's launch_tests step: it runs the test-launcher-back (Karate) STABLE image on the host network against the already-running app and mocks, mounting the feature files and writing the HTML report to the host, and can open that report in a browser.
|
Package stablekarate reproduces the legacy DIA component tool's launch_tests step: it runs the test-launcher-back (Karate) STABLE image on the host network against the already-running app and mocks, mounting the feature files and writing the HTML report to the host, and can open that report in a browser. |
Click to show internal directories.
Click to hide internal directories.