docs: Unification of documentation

.github/ISSUE_TEMPLATE/2-new-workload.md

@@ -15,17 +15,16 @@ assignees: ""
 - tbd
 
 **Test Category Name**
-- ADD CATEGORY_NAME (e.g. State, Security, etc from [README](https://github.com/cncf/cnf-testsuite/blob/main/README.md#cnf-testsuite))
+- ADD CATEGORY_NAME (e.g. State, Security, etc from [README](../../README.md#cnf-testsuite))
 
 **Type of test (static or runtime)**
 - tbd
 
 ---
 
 ### Documentation tasks:
-- [ ] Update [installation instructions](https://github.com/cncf/cnf-testsuite/blob/main/install.md) if needed
-- [ ] Update [Test Categories md](https://github.com/cncf/cnf-testsuite/blob/main/TEST-CATEGORIES.md) if needed
-- [ ] Update [USAGE md](https://github.com/cncf/cnf-testsuite/blob/main/USAGE.md) if needed
+- [ ] Update [installation instructions](../../INSTALL.md) if needed
+- [ ] Update [TEST_DOCUMENTATION md](../../docs/TEST_DOCUMENTATION.md) if needed
   - [ ] How to run
   - [ ] Description and details
     - [ ] What the best practice is

.github/ISSUE_TEMPLATE/3-new-platform.md

@@ -48,10 +48,9 @@ assignees: ""
 
 **Documentation tasks:**
 
-- [ ] Update [Test Categories md](https://github.com/cncf/cnf-testsuite/blob/main/TEST-CATEGORIES.md) if needed
 - [ ] Update [Pseudo Code md](https://github.com/cncf/cnf-testsuite/blob/main/PSEUDO-CODE.md) if needed
-- [ ] Update [USAGE md](https://github.com/cncf/cnf-testsuite/blob/main/USAGE.md) if needed
-- [ ] Update [installation instructions](https://github.com/cncf/cnf-testsuite/install.md) if needed
+- [ ] Update [TEST_DOCUMENTATION md](../../docs/TEST_DOCUMENTATION.md) if needed
+- [ ] Update [installation instructions](../../install.md) if needed
 
 ### QA tasks
 

.github/ISSUE_TEMPLATE/ignore/5-proof-of-concept.md

@@ -19,8 +19,8 @@ Tasks:
 - [ ] Select a tool to use, minimal/least effort, and add selection to ticket
 - [ ] Add new POC test code
 - [ ] Add comment suggesting updates as needed for:
-  - [ ] the [test categories markdown](https://github.com/cncf/cnf-testsuite/blob/main/TEST-CATEGORIES.md)
-  - [ ] the [psuedo code markdown](https://github.com/cncf/cnf-testsuite/blob/main/PSEUDO-CODE.md)
+  - [ ] the [TEST_DOCUMENTATION md](../../../docs/TEST_DOCUMENTATION.md)
+  - [ ] the [psuedo code markdown](../../../PSEUDO-CODE.md)
   - [ ] slide content updates, LINK_TO_UPDATES
-  - [ ] the [README](https://github.com/cncf/cnf-testsuite/blob/main/README.md)
+  - [ ] the [README](../../../README.md)
 - [ ] Tag 1 or more people to peer review

CNF_TESTSUITE_YML_USAGE.md

@@ -103,7 +103,7 @@ Example Setting:
 
 #### helm_install_namespace
 
-This sets the namespace that helm will use to install the CNF to. This is to conform to the best practice of not installing your CNF to the `default` namespace on your cluster. You can learn more about this practice [here](./docs/LIST_OF_TESTS.md#default-namespaces). This is an optional setting but highly recommended as installing your CNF to use the `default` namespace will result with failed tests.
+This sets the namespace that helm will use to install the CNF to. This is to conform to the best practice of not installing your CNF to the `default` namespace on your cluster. You can learn more about this practice [here](./docs/TEST_DOCUMENTATION.md#default-namespaces). This is an optional setting but highly recommended as installing your CNF to use the `default` namespace will result with failed tests.
 
 You can learn more about kubernetes namespaces [here](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/)
 

README.md

@@ -38,7 +38,7 @@ The CNTI Test Catalog will inspect CNFs for the following characteristics:
 - **Observability & Diagnostics** - CNFs should externalize their internal states in a way that supports metrics, tracing, and logging.
 - **Security** - CNF containers should be isolated from one another and the host. CNFs are to be verified against any common CVE or other vulnerabilities.
 
-See the [Test Categories Documentation](TEST-CATEGORIES.md) for a complete overview of the tests.
+See the [Complete Test Documentation](docs/TEST_DOCUMENTATION.md) for a complete overview of the tests.
 
 ## Contributing
 

ROADMAP.md

@@ -12,10 +12,10 @@ To get a more complete overview of planned features and current work see the [pr
 - Build tests for Kubernetes best practices that address issues voiced by the end users, including:
     - On-boarding (day 1) items
     - CNF WG best practices
-- Build [resilience tests](https://github.com/cnti-testcatalog/testsuite/blob/main/USAGE.md#resilience-tests) using [LitmusChaos](https://litmuschaos.io/) experiments
-- Create [observability tests](https://github.com/cnti-testcatalog/testsuite/blob/main/USAGE.md#observability-tests) to check for cloud native monitoring
-- Create [state tests](https://github.com/cnti-testcatalog/testsuite/blob/main/USAGE.md#state-tests) to check cloud native data handling
-- Create [security tests](https://github.com/cnti-testcatalog/testsuite/blob/main/USAGE.md#security-tests)
+- Build [resilience tests](https://github.com/cnti-testcatalog/testsuite/blob/main/docs/TEST_DOCUMENTATION.md#category-reliability-resilience--availability-tests) using [LitmusChaos](https://litmuschaos.io/) experiments
+- Create [observability tests](https://github.com/cnti-testcatalog/testsuite/blob/main/docs/TEST_DOCUMENTATION.md#category-observability--diagnostic-tests) to check for cloud native monitoring
+- Create [state tests](https://github.com/cnti-testcatalog/testsuite/blob/main/docs/TEST_DOCUMENTATION.md#category-state-tests) to check cloud native data handling
+- Create [security tests](https://github.com/cnti-testcatalog/testsuite/blob/main/docs/TEST_DOCUMENTATION.md#category-security-tests)
 
 ### Enhance the functionality of the test suite framework