Skip to content

Commit 043eb9e

Browse files
committed
tests: Update Readme
Signed-off-by: vbedida79 <veenadhari.bedida@intel.com>
1 parent 4858324 commit 043eb9e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

tests/README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,20 +2,20 @@
22
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.
33

44
#### L1 First Layer: Host OS and Driver Interfaces
5-
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](https://github.com/intel/intel-data-center-gpu-driver-for-openshift/blob/main/README.md). It includes test cases :
5+
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 :
66
* to check existence of in-tree and OOT tree drivers
77
* for SELinux and host OS security
88
* check for devices on all nodes
99

1010
#### L2 Second Layer: Device plugin resource provisioning
11-
L2 test cases are executed after deploying the [Intel Device Plugins Operator](device_plugins/README.md). Refer to [readme](l2/README.md). It includes:
11+
L2 test cases are executed after deploying the [Intel Device Plugins Operator](/device_plugins/README.md). Refer to [readme](l2/README.md). It includes:
1212
* Pod's resource allocation and scheduling
1313
* Simple workloads
1414
* Boundary testing for the resources
1515
* Future plan for any failure analysis needed during automation.
1616

1717
#### L3 Third Layer: E2E solution
18-
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.
18+
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.
1919

2020
#### L4 Fourth Layer: Reference Workloads
2121
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)