SWDEV-420894 - Remove directed tests

Point users to correct hip-tests path.
Remove references of directed test from code.
Replace documentation which used directed test with a native sample.

Change-Id: I3e8b5b5b40c0847e03d3aa637ea5b0c0d06c1201

docs/developer_guide/build.md

@@ -123,47 +123,14 @@ hip_prof_gen.py -v -p -t --priv <hip>/include/hip/hip_runtime_api.h \
 
 ### Build HIP tests
 
-#### Build HIP directed tests
-Developers can build HIP directed tests right after build HIP commands,
-
-```shell
-sudo make install
-make -j$(nproc) build_tests
-```
-By default, all HIP directed tests will be built and generated under the folder `$CLR_DIR/build/hipamd`directed_tests.
-Take HIP directed device APIs tests, as an example, all available test applications will have executable files generated under,
-`$CLR_DIR/build/hipamd/directed_tests/runtimeApi/device`.
-
-Run all HIP directed_tests, use the command,
-
-```shell
-ctest
-```
-Or
-```shell
-make test
-```
-
-Build and run a single directed test, use the follow command as an example,
-
-```shell
-make directed_tests.texture.hipTexObjPitch
-cd $CLR_DIR/build/hipamd/directed_tests/texcture
-./hipTexObjPitch
-```
-Please note, the integrated HIP directed tests, will be deprecated in future release.
-
-
-##### Build HIP catch tests
-
 HIP catch tests, with new architectured Catch2, are official seperated from HIP project, exist in HIP tests repository, can be built via the following instructions.
 
-##### Get HIP tests source code
+#### Get HIP tests source code
 
 ```shell
 git clone -b "$ROCM_BRANCH" https://github.com/ROCm-Developer-Tools/hip-tests.git
 ```
-##### Build HIP tests from source
+#### Build HIP tests from source
 
 ```shell
 export HIPTESTS_DIR="$(readlink -f hip-tests)"
@@ -183,7 +150,7 @@ cd $HIPTESTS_DIR/build/catch_tests/unit/texture
 ./TextureTest
 ```
 
-##### Build HIP Catch2 standalone test
+#### Build HIP Catch2 standalone test
 
 HIP Catch2 supports build a standalone test, for example,
 

docs/developer_guide/contributing.md

@@ -59,16 +59,16 @@ Selected multilib: .;@m64
 
 ## Unit Testing Environment
 
-HIP includes unit tests in the tests/src directory.
-When adding a new HIP feature, add a new unit test as well.
-See [tests/README.md](README.md) for more information.
+Tests for HIP are hosted at [ROCm-Developer-Tools/hip-tests](https://github.com/ROCm-Developer-Tools/hip-tests).
+
+To run `hip-tests` please go to the repo and follow the steps.
 
 ## Development Flow
 
-Directed tests provide a great place to develop new features alongside the associated test.
+`hip-tests` provide a great place to develop new features alongside the associated test.
 
-For applications and benchmarks outside the directed test environment, developments should use a two-step development flow:
-- #1. Compile, link, and install HIP/ROCclr.  See [Installation](README.md#Installation) notes.
+For applications and benchmarks outside the hip-tests environment, developments should use a two-step development flow:
+- #1. Compile, link, and install HIP/ROCclr. See [Installation](README.md#Installation) notes.
 - #2. Relink the target application to include changes in HIP runtime file.
 
 ## Environment Variables
@@ -124,13 +124,7 @@ Differences or limitations of HIP APIs as compared to CUDA APIs should be clearl
 
 
 ### Presubmit Testing:
-Before checking in or submitting a pull request, run all directed tests (see tests/README.md) and all Rodinia tests.
-Ensure pass results match starting point:
-
-```console
-> cd examples/
-> ./run_all.sh
-```
+Before checking in or submitting a pull request, run all hip-tests (see [ROCm-Developer-Tools/hip-tests](https://github.com/ROCm-Developer-Tools/hip-tests)).
 
 
 ### Checkin messages