CDISC Builder™  2.1 - Installation Test Scripts - %relrec
The following documentation contains test scripts and expected results for validating the CDISC Builder tool.  Do the following to verify proper installation:
  • Start CDISC Builder application by double clicking on the desktop icon.
  • Perform each test by performing the steps specified by the instructions.  
  • Evaluate the results of each step by comparing them with results described in the Documentation column. 
Script Description Documentation
relrec1.sas Verify for missing required parameters. Instructions 1
relrec1.log
relrec2.sas Test the condition where the OUTPUT parameter is missing. Instructions 2
Test the condition where the OUTPUT parameter is one level name. relrec2.log
relrec3.sas Verify if specified data does not exist Instructions 3
relrec3.log
relrec4.sas Verify that the usubjid exists as a variable in the dataset. Instructions 4
relrec4.log
relrec5.sas If specified, verify if the IDVAR does not exist in the dataset.  Instructions 5
relrec5.log
relrec6a.sas Verify that a new OUTPUT data RELREC is created. 

Instructions 6a

relrec6a.log
relrec6b.sas Verify that an existing OUTPUT data RELREC has been updated with the proper variables. 

Instructions 6b

relrec6b.log

relrec7.sas Verify the output data IDVAR and IDVAL has the correct value according to input. Instructions 7
relrec7.sas7bdat
relrec8.sas Verify the output data USUBJID has the correct value according to input.

Instructions 8

relrec8.log

relrec8.sas7bdat
relrec9.sas Verify that the RELTYPE is either ONE or MANY Instructions 9
relrec9.sas7bdat
relrec10.sas Test the creating basecode file Instructions 10
relrec10.sas7bdat
testbasecode.sas

Instructions 1
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "saspgm".

  2. Right mouse click on the relrec1.sas program and select "Batch Submit".

  3. Review the relrec1.log file and verify that the following messages are produced.

    • ERROR: [relrec] is missing required parameter DATA.

    • ERROR: [relrec] is missing required parameter RDOMAIN.

    • ERROR: [relrec] is missing required parameter STUDYID.

    • ERROR: [relrec] is missing required parameter USUBJID.

  4. This can be verified against the relrec1.log found in the benchmark area.

Instructions 2
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "data".

  2. Delete relrec and relrec2 datasets if they exist.

  3. Navigate to the validation sub-directory named "saspgm".

  4. Right mouse click on the relrec2.sas program and select "Batch Submit".

  5. Review the relrec2.log file and verify that the following message is produced.

    • NOTE: [relrec] has created the new output data: dataware.relrec (label="Related Records")

    • NOTE: [relrec] has created the new output data: dataware.relrec2 (label="Related Records")

  6. This can be verified against the relrec2.log found in the benchmark area.

Instructions 3
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "saspgm".

  2. Right mouse click on the relrec3.sas program and select "Batch Submit".

  3. Review the relrec3.log file and verify that the following message is produced.

    • ERROR: [relrec] specified data dataware.notexist does not exist. 

  4. This can be verified against the relrec3.log found in the benchmark area.  

Instructions 4
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "saspgm".

  2. Right mouse click on the relrec4.sas program and select "Batch Submit".

  3. Review the relrec4.log file and verify that the following message is produced.

    • ERROR: [relrec] has an invalid USUBJID specified. 

  4. The relrec4.log is available in the benchmark area for comparisons.

Instructions 5
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "saspgm".

  2. Right mouse click on the relrec5.sas program and select "Batch Submit".

  3. Review the relrec5.log file and verify that the following message is produced.

    • ERROR: [relrec] has an invalid IDVAR: notexist specified.

  4. A similar version can be reviewed and compared in the benchmark area.

Instructions 6a
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "data".

  2. Delete relrec6 datasets if it exists.

  3. Navigate to the validation sub-directory named "saspgm".

  4. Right mouse click on the relrec6a.sas program and select "Batch Submit".

  5. Review the relrec6a.log file and verify that the following message is produced.

    • NOTE: [relrec] has created the new output data: dataware.relrec6 (label="Related Records")

  6. Verify that there is relrec6 dataset created in data folder.

  7. Open relrec6 dataset and verify that the idvar has the value=occnum.

Instructions 6b
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "saspgm".

  2. Right mouse click on the relrec6b.sas program and select "Batch Submit".

  3. Review the relrec6b.log file and verify that the following message is produced.

    • NOTE: [relrec] has updated the existing output data: dataware.relrec6 (label="Related Records")
      located at: C:\test\test_relrec_GUI\testing\data

  4. Verify that relrec6 dataset has been updated with the new variables.  Now the idvar variable has the new value=ptid.

Notes: the path of the dataset may be different due to the location of the data. 

Instructions 7
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "saspgm".

  2. Right mouse click on the relrec7.sas program and select "Batch Submit".

  3. Review the relrec7.log file to ensure that there are no error messages.

  4. Navigate to the sub-directory named "data" and open ae dataset.

  5. Verify that the LINE variable contains values 1, 2, 3.

  6. Open relrec7 dataset.

  7. Verify that IDVAR variable captures "line" value and IDVARVAL captures values of LINE variable from ae dataset.

Instructions 8
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "saspgm".

  2. Right mouse click on the relrec8.sas program and select "Batch Submit".

  3. Review the relrec8.log file to ensure that there are no error messages.

  4. Open relrec8 dataset in data folder and verify that the USUBJID  has the value between 1 and 3.

Instructions 9
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation sub-directory named "saspgm".

  2. Right mouse click on the relrec9.sas program and select "Batch Submit".

  3. Review the relrec9.log file to ensure that there are no error messages.

  4. Navigate to the sub-directory named "data" and open relrec9 dataset.

  5. Verify that domain named "ae" in RDOMAIN column matches with only "dataware.ae" in RELID column, so the RELTYPE variable has "ONE" value.  Domain named "ae1" in RDOMAIN column match with both "dataware.ae1" and "dataware.ae2"  in RELID column, so the RELTYPE variable has "MANY" value 

  6. A similar version can be reviewed and compared in the benchmark area.

Instructions 10
The following instructions are accomplished through Windows Explorer.

  1. Delete relrec10 dataset in validation sub-directory named "data" if it exists.

  2. Navigate to the validation sub-directory named "saspgm".

  3. Right mouse click on the relrec10.sas program and select "Batch Submit".

  4. Review the relrec10.log file to ensure that there are no error messages.

  5. Rename "relrec10.sas7bdat" to "relrec10_rename.sas7bdat" in "data" sub-directory.

  6. Verify the creating a basecode file named "testbasecode.sas". 

  7. Batch submit "testbasecode.sas".  Verify that a "relrec10" dataset is created.     

  8. Compare "relrec10" dataset to "relrec10_rename" dataset to ensure that they are similar.

  9. A similar version can be reviewed and compared in the benchmark area.

For more information, please contact MXI .

 
     Meta-Xceed Inc. © 2009