Skip to content

Commit c8efaa6

Browse files
committed
tests: Updated readme
Signed-off-by: vbedida79 <veenadhari.bedida@intel.com>
1 parent c3ab0dd commit c8efaa6

File tree

1 file changed

+11
-8
lines changed

1 file changed

+11
-8
lines changed

tests/README.md

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,27 @@
1-
## Disclaimer
1+
# Test Plan
2+
3+
```{admonition} Disclaimer
24
Please note that this module is currently under development and may contain partially implemented features, therefore it is not supported in the current release.
5+
```
36

4-
## Test plan and architecture overview
7+
## Overview
58
To ensure the whole stack is working as expected and track bugs, a layer based test architecture is needed on OCP. This plan consists of four layers. The first and second layers mentioned below, would be a part of the future automation testing framework on each OCP (x,y,z) release.
69

7-
#### L1 First Layer: Host OS and Driver Interfaces
8-
Layer 1 test cases should be executed before deploying [Intel Device Plugins Operator](/device_plugins/README.md) and after deploying OOT drivers like [Intel Data Center GPU Driver on OpenShift](/kmmo/README.md#managing-intel-dgpu-driver-with-kmm-operator). It includes test cases :
10+
### L1 First Layer: Host OS and Driver Interfaces
11+
Layer 1 test cases should be executed before deploying [Intel Device Plugins Operator](/device_plugins/README.md) and after deploying OOT drivers like [Intel Data Center GPU Driver on OpenShift](/kmmo/README.md). It includes test cases :
912
* to check existence of in-tree and OOT tree drivers
1013
* for SELinux and host OS security
1114
* check for devices on all nodes
1215

13-
#### L2 Second Layer: Device plugin resource provisioning
16+
### L2 Second Layer: Device Plugin Resource Provisioning
1417
L2 test cases are executed after deploying the [Intel Device Plugins Operator](/device_plugins/README.md). Refer to [readme](l2/README.md). It includes:
1518
* Pod's resource allocation and scheduling
1619
* Simple workloads
1720
* Boundary testing for the resources
1821
* Future plan for any failure analysis needed during automation.
1922

20-
#### L3 Third Layer: E2E solution
21-
L3 test cases are executed after the specific device plugin related e2e solution has been deployed in [day 2](/README.md#day-2---ocp-platform-is-installed-and-ready-to-begin-providing-services). Please refer to [L3 test cases](l3/README.md) for detail.
23+
### L3 Third Layer: E2E solution
24+
L3 test cases are executed after the specific device plugin related [e2e solution](/e2e) has been deployed. Please refer to [L3 test cases](l3/README.md) for detail.
2225

23-
#### L4 Fourth Layer: Reference Workloads
26+
### L4 Fourth Layer: Reference Workloads
2427
This layer includes the reference final application/usecase for the user. It integrates the whole stack and is custom for each Intel hardware feature and device plugin. This layer is yet to be added in upcoming releases.

0 commit comments

Comments
 (0)