67a2ab1438
The simple test script has gotten out of control. Shard this script into different pieces and attempt to impose order on overall test structure. This change helps lay some of the foundations for future improvements. * The runsc/test directories are moved into just test/. * The runsc/test/testutil package is split into logical pieces. * The scripts/ directory contains new top-level targets. * Each test is now responsible for building targets it requires. * The install functionality is moved into `runsc` itself for simplicity. * The existing kokoro run_tests.sh file now just calls all (can be split). After this change is merged, I will create multiple distinct workflows for Kokoro, one for each of the scripts currently targeted by `run_tests.sh` today, which should dramatically reduce the time-to-run for the Kokoro tests, and provides a better foundation for further improvements to the infrastructure. PiperOrigin-RevId: 267081397 |
||
---|---|---|
.. | ||
common | ||
go | ||
java | ||
nodejs | ||
php | ||
python | ||
BUILD | ||
README.md | ||
build_defs.bzl | ||
runtimes.go | ||
runtimes_test.go |
README.md
Runtimes Tests Dockerfiles
The Dockerfiles defined under this path are configured to host the execution of the runtimes language tests. Each Dockerfile can support the language indicated by its directory.
The following runtimes are currently supported:
- Go 1.12
- Java 11
- Node.js 12
- PHP 7.3
- Python 3.7
Prerequisites:
-
Build each Docker container from the runtimes directory:
$ docker build -f $LANG/Dockerfile [-t $NAME] .
Testing:
If the prerequisites have been fulfilled, you can run the tests with the following command:
$ docker run --rm -it $NAME [FLAG]
Running the command with no flags will cause all the available tests to execute.
Flags can be added for additional functionality:
- --list: Print a list of all available tests
- --test <name>: Run a single test from the list of available tests
- --v: Print the language version