github/containerd
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

added make help for cri integration

Browse Source 
Signed-off-by: Jordan Karaze <jordan.karaze@ibm.com>
This commit is contained in:
Jordan Karaze
2022-03-28 15:19:21 -05:00
parent d394e00c7e
commit cf571fa968
3 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
BUILDING.md
View File

@@ -237,6 +237,7 @@ During the automated CI the unit tests and integration tests are run as part of
- `make test`: run all non-integration tests that do not require `root` privileges - `make test`: run all non-integration tests that do not require `root` privileges
- `make root-test`: run all non-integration tests which require `root` - `make root-test`: run all non-integration tests which require `root`
- `make integration`: run all tests, including integration tests and those which require `root`. `TESTFLAGS_PARALLEL` can be used to control parallelism. For example, `TESTFLAGS_PARALLEL=1 make integration` will lead a non-parallel execution. The default value of `TESTFLAGS_PARALLEL` is **8**. - `make integration`: run all tests, including integration tests and those which require `root`. `TESTFLAGS_PARALLEL` can be used to control parallelism. For example, `TESTFLAGS_PARALLEL=1 make integration` will lead a non-parallel execution. The default value of `TESTFLAGS_PARALLEL` is **8**.
- `make cri-integration`: [CRI Integration Tests](https://github.com/containerd/containerd/blob/main/docs/cri/testing.md#cri-integration-test) run cri integration tests
To execute a specific test or set of tests you can use the `go test` capabilities To execute a specific test or set of tests you can use the `go test` capabilities
without using the `Makefile` targets. The following examples show how to specify a test without using the `Makefile` targets. The following examples show how to specify a test

2
Makefile
View File

@@ -209,7 +209,7 @@ bin/cri-integration.test:
@echo "$(WHALE) $@" @echo "$(WHALE) $@"
@$(GO) test -c ./integration -o bin/cri-integration.test @$(GO) test -c ./integration -o bin/cri-integration.test
cri-integration: binaries bin/cri-integration.test ## run cri integration tests cri-integration: binaries bin/cri-integration.test ## run cri integration tests (example: FOCUS=TestContainerListStats make cri-integration)
@echo "$(WHALE) $@" @echo "$(WHALE) $@"
@bash -x ./script/test/cri-integration.sh @bash -x ./script/test/cri-integration.sh
@rm -rf bin/cri-integration.test @rm -rf bin/cri-integration.test

11
docs/cri/testing.md
View File

@@ -8,10 +8,19 @@ Before sending pull requests you should at least make sure your changes have pas
Follow the [building](../../BUILDING.md) instructions. Follow the [building](../../BUILDING.md) instructions.
## CRI Integration Test ## CRI Integration Test
* Run CRI integration test: * Run all CRI integration tests:
```bash ```bash
make cri-integration make cri-integration
``` ```
* Run specific CRI integration tests: use the `FOCUS` parameter to specify the test case.
```bash
# run CRI integration tests that match the test string <TEST_NAME>
FOCUS=<TEST_NAME> make cri-integration
```
Example:
```bash
FOCUS=TestContainerListStats make cri-integration
```
## CRI Validation Test ## CRI Validation Test
[CRI validation test](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/validation.md) is a test framework for validating that a Container Runtime Interface (CRI) implementation such as containerd with the `cri` plugin meets all the requirements necessary to manage pod sandboxes, containers, images etc. [CRI validation test](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/validation.md) is a test framework for validating that a Container Runtime Interface (CRI) implementation such as containerd with the `cri` plugin meets all the requirements necessary to manage pod sandboxes, containers, images etc.