Adjust paths for impending moves to the framework

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>

docs/architecture/testing/test-framework.md

@@ -22,7 +22,7 @@ Each test case has a description which succinctly describes for a human audience
 * Make the description descriptive. “foo: x=2, y=4” is more descriptive than “foo #2”. “foo: 0<x<y, both even” is even better if these inequalities and parities are why this particular test data was chosen.
 * Avoid changing the description of an existing test case without a good reason. This breaks the tracking of failures across CI runs, since this tracking is based on the descriptions.
 
-`tests/scripts/check_test_cases.py` enforces some rules and warns if some guidelines are violated.
+`framework/scripts/check_test_cases.py` enforces some rules and warns if some guidelines are violated.
 
 ## TLS tests
 

tests/scripts/analyze_outcomes.py

@@ -8,7 +8,8 @@ less likely to be useful.
 
 import re
 
-import outcome_analysis
+import scripts_path # pylint: disable=unused-import
+from mbedtls_framework import outcome_analysis
 
 
 class CoverageTask(outcome_analysis.CoverageTask):

tests/scripts/check_test_cases.py

@@ -14,7 +14,7 @@ import re
 import sys
 
 import scripts_path # pylint: disable=unused-import
-import collect_test_cases
+from mbedtls_framework import collect_test_cases
 
 
 class DescriptionChecker(collect_test_cases.TestDescriptionExplorer):

tests/scripts/components-basic-checks.sh

@@ -70,7 +70,7 @@ component_check_test_cases () {
     else
         opt=''
     fi
-    tests/scripts/check_test_cases.py -q $opt
+    framework/scripts/check_test_cases.py -q $opt
     unset opt
 }