Improvments

docs/specifications/tests/README.md

@@ -20,7 +20,8 @@ project. All the details are in the [Master Test Plan](MasterTestPlan.md).
 2. Under each test level directory there is a level document (README.md)
    describing the test level. See for example the level document from
    [Syntax-TP](Syntax-TP/README.md).
-3. The level document (README.md) describes the mapping from Test Requirement
+3. The level document (the README.md in the test level directory) describes 
+   the mapping from Test Requirement
    to each individual Test Case document.
 
 ## Elaboration of the test case
@@ -33,7 +34,8 @@ project. All the details are in the [Master Test Plan](MasterTestPlan.md).
 ## Document Hierarchy
 
 1. Each Test Level described in [Master Test Plan](MasterTestPlan.md)
-   should be linked directly to the correct level document (README.md).
+   should be linked directly to the correct level document (the README.md
+   in the test level directory).
 2. Each Test Case in the Test Level document should be linked directly
    to the correct Test Case document.
 

utils/maprequirement.pl

@@ -229,8 +229,8 @@ sub outputResult {
 				$otcDesc = $testInfo->{'desc'};
 				$oLevel  = $testInfo->{'level'};
 				my $linkID = "[$otcID]($otcLink)";
-				printf "|%3s|%23s|[%10s](%s/$levelfile)|%-10s|%17s|\n",
-						$oReqID,$oReqText,$oLevel,$oLevel,$linkID,$otcDesc;
+				printf "|%3s|%23s|[%10s](%s/%s)|%-10s|%17s|\n",
+						$oReqID,$oReqText,$oLevel,$oLevel,$levelfile,$linkID,$otcDesc;
 			}
 		}
 	}