Test scripts, automation

Examples of test data sets available (e.g., test scripts or automated test tools that would be suitable for version purchased) Boundary/stress/unexpected input tests Structural/functional testing (documentation of walkthroughs, etc.)... 

According to the proposed workflow, test cases can be analyzed (at the state this is not automated) and, if they are rejected by engineers, some updates on the source specifications can be performed. Test cases are then transformed into executable test scripts, through a transformation in the lOP notation. This language supports the creation of interoperable and multi-supplier testing environments. 

Figure 11-4. Purity assessment is a critical component in the decision process by the chemist as to whether their isolated compound is of sufficient quality to be submitted for compound registration and biological testing. To facilitate automated and rapid purity assessment of compound libraries, applescripts and visual basic scripts are used. (A) Total ion current chromatogram shows two components. (B) Extracted ion chromatogram for the expected product identifies its retention time. (C) Mass spectrum observed for the expected product. (D) UV 220-nm chromatogram indicates the expected product is approximately 75% pure. (E) UV 254-nm chromatogram indicates the expected product is approximately 66% pure.

Alternatively, if the decision is made to buy only commercially available software, or only commercially developed add-ons or automation scripts, then the pharmacometrician needs to participate in the key processes used to evaluate the vendor. The occurrence of key quality failures in widely used software has been previously documented (14). Therefore, the pharmacometrician should be intimately involved in the vendor audit process. If the vendor is not performing the quality assurance procedures just outlined for internal development, the cost (both in quality and accuracy of future work) will be in jeopardy. As discussed later in the section on validation documentation, the ability to state what the vendor s quality processes are will mitigate the need to perform functional software testing at the same level that has already been executed by the vendor s quality assurance group. 

To use standalone BLAST to generate a BugView genome comparison file it is necessary to perform successive comparisons of protein sequences. A Perl script to automate this, gcfprep, can be downloaded from http //www.gla.ac.uk/ dplln/BugView/bvdownload.html. This script has only been tested on standalone BLAST running under Solaris, and may need modification to run on other platforms. 

---