77833ece3b
proctor-go had a bug where it would incorrectly identify a tool test as a disk test. Instead of searching for the test on disk as the identification method, we now check if the test name ends in ".go". If the test ends in ".go" it is run as a disk test, otherwise the test is run as a tool test. Python tests need to be run from within the directory they exist. Functionality to split the test name from it's parent directory has been added and a cmd.Dir argument has been set. PiperOrigin-RevId: 261021693 |
||
|---|---|---|
| .. | ||
| common | ||
| go | ||
| java | ||
| nodejs | ||
| php | ||
| python | ||
| BUILD | ||
| README.md | ||
| 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:
$ 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