Programmer's ROM - The Computer Language Library

home *** CD-ROM | disk | FTP | other *** search

/ Programmer's ROM - The Computer Language Library / programmersrom.iso / ada / forms / form2.doc < prev next >

Wrap

Text File | 1988-05-03 | 66.8 KB | 4,577 lines

||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| Computer Program Test Procedures for a Forms Generator System in Ada Prepared for: ||||||||||||||||||||||||| ||||||||||||||||||||||||| Advanced Computer Systems Lab ||||||||||||||||||||||||| Texas Instruments ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| Equipment Group - ACSL ||||||||||||||||||||||||| P.O. Box 801, M.S. 8007 ||||||||||||||||||||||||| McKinney, Texas 75069 ||||||||||||||||||||||||| 15 January 1985 ||||||||||||||||||||||||| ||||||||||||||||||||||||| TEXAS INSTRUMENTS INCORPORATED ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| CONTENTS CHAPTER 1 INTRODUCTION PURPOSE . . . . . . . . . . . . . . . . . . . . . 1-1 SCOPE . . . . . . . . . . . . . . . . . . . . . . 1-1 SUMMARY . . . . . . . . . . . . . . . . . . . . . 1-1 CHAPTER 2 APPLICABLE DOCUMENTS CHAPTER 3 TESTING REQUIREMENTS GENERAL . . . . . . . . . . . . . . . . . . . . . 3-1 FORMS GENERATOR ACCEPTANCE/PREOPERATING PROCEDURES 3-2 EQUIPMENT PREPARATION . . . . . . . . . . . . . . 3-2 DIGITAL PROCESSOR PREPARATION . . . . . . . . . . 3-2 TESTING PROCEDURE . . . . . . . . . . . . . . . . 3-2 CHAPTER 4 TEST MANAGEMENT CHAPTER 5 PERSONNEL REQUIREMENTS CHAPTER 6 HARDWARE REQUIREMENTS CHAPTER 7 SOFTWARE REQUIREMENTS CHAPTER 8 TESTING SCHEDULE CHAPTER 9 QUALITY ASSURANCE APPENDIX A TEST SPECIFICATIONS CREATE/LOAD FORM . . . . . . . . . . . . . . . . . A-2 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-2 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-2 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-2 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-2 EDIT FORM 1 . . . . . . . . . . . . . . . . . . . A-4 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-4 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-4 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-4 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-4 EDIT FORM 2 . . . . . . . . . . . . . . . . . . . A-6 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-6 Page 2 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-6 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-6 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-6 EDIT FORM 3 . . . . . . . . . . . . . . . . . . . A-8 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-8 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-8 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-8 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-8 EDIT FORM 4 . . . . . . . . . . . . . . . . . . A-10 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-10 DESCRIPTION OF TEST . . . . . . . . . . . . . A-10 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-10 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-10 MODIFY FORM . . . . . . . . . . . . . . . . . . A-12 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-12 DESCRIPTION OF TEST . . . . . . . . . . . . . A-12 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-12 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-12 SAVE FORM . . . . . . . . . . . . . . . . . . . A-14 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-14 DESCRIPTION OF TEST . . . . . . . . . . . . . A-14 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-14 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-14 EXIT INTERACTIVE FORM GENERATOR . . . . . . . . A-16 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-16 DESCRIPTION OF TEST . . . . . . . . . . . . . A-16 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-16 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-16 BATCH FORMS GENERATOR . . . . . . . . . . . . . A-18 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-18 DESCRIPTION OF TEST . . . . . . . . . . . . . A-18 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-18 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-18 FORM EXECUTOR . . . . . . . . . . . . . . . . . A-20 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-20 DESCRIPTION OF TEST . . . . . . . . . . . . . A-20 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-20 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-20 APPENDIX B CROSS-REFERENCE MATRICES TEST/REQUIREMENTS MATRIX . . . . . . . . . . . . . B-1 REQUIREMENTS/TEST MATRIX . . . . . . . . . . . . . B-2 TEST FILE MATRIX . . . . . . . . . . . . . . . . . B-4 APPENDIX C GLOSSARY CHAPTER 1 INTRODUCTION This Computer Program Test Procedures document is divided into two major sections: (1) Sections (that have numeric prefixes) which provide background information for the tests and (2) Appendices (that have alphabetic prefixes) which contain the tests themselves. 1.1 PURPOSE This Computer Program Test Procedures document describes the acceptance test procedures for the Forms Generator computer program. This research and development is being done for the Naval Ocean Systems Center (NOSC) under contract N66001-84-R0030. Items 44 and 47 are the Forms Generator System. Within this document, the Forms Generator System is occasionally referred to as the Forms Generator or the FG. This acceptance test procedures document has been prepared in accordance with the Navy Data Item Description for a Computer Program Test Procedures document [NAV78A]. 1.2 SCOPE This document describes the procedures for testing the Forms Generator after it is developed. The test procedures defined in this document will show compliance with the requirements of the proposal. 1.3 SUMMARY The objective of this document is to explain the test procedures that are necessary for acceptance testing of the Forms Generator. Acceptance testing will demonstrate that the requirements of the proposal have been satisfied. A list of the requirements that must be verified is provided in the Requirements Cross Reference Matrix in Appendix B. 1-1 CHAPTER 2 APPLICABLE DOCUMENTS ________ ______ _______ ___ _______ [BEI84] Beizer, Borix, Software System Testing and Quality _________ Assurance, Van Nostrand Reinhold Co., New York, 1984. ___ ________ [BRU82] Bruce, Phillip and Sam M. Pederson, The Software ___________ _______ Development Project, John Wiley and Sons, Inc., New York, 1982. __________ ________ ____ [EVA84] Evans, Michael W., Productive Software Test __________ Management, John Wiley and Sons, Inc., New York, 1984. ___ ___ __ ________ _______ [MYE79] Myers, Glenford J., The Art of Software Testing, John Wiley and Sons, Inc., New York, 1979. [NAV78A] Navy, "Data Item Description, Computer Program Test Procedures", Navy DI-T2144, 29 November 1978. [NAV78B] Navy, "Data Item Description, Computer Program Test Procedures", Navy DI-E-2143, 29 November 1978. [TI84 ] Texas Instruments, Proposals Associated with the Forms Generator System, Lewisville, Tx, January 1984. 2-1 CHAPTER 3 TESTING REQUIREMENTS 3.1 GENERAL Acceptance testing of the Forms Generator must verify the requirements in the proposal [TI84] for the Forms Generator. A summary of the requirements from the proposal document is provided in Appendix B in the Requirements Cross Reference Matrix. Verifying that the requirements have been satisfied is a process involving three main steps. A description of each step is given below. 1. Develop Test Specifications - The first step is to develop test specifications based on the requirements. The test specifications outline the testing criteria that is necessary to show that the Forms Generator satisfies its original objectives. Appendix A contains the test specifications for the Forms Generator. 2. Create Test Data - The second step is to create test data to satisfy the test specifications. The test data is a library of Ada source programs (which tests the Forms Executor), a library of Batch Forms Generator tests, and libraries of keystroke files which test the Interactive Forms Generator and the Forms Executor. 3. Analyze Results - The third step is to conduct testing and analyze the results. The Forms Generator is executed with the test data and test programs that was created in step 2. The results are analyzed and the appropriate matrices are updated. Some of the ideas from Myers [MYE79] were used to facilitate the development of the test specifications. Specifically, three acceptance test categories (facility, volume, and usability) defined by Myers were used to help define the test specifications. Myers' definitions for facility testing, volume testing, and usability testing are provided below. 3-1 TESTING REQUIREMENTS Facility Facility testing is the determination of whether each facility or function is actually implemented. The procedure is to scan the requirements sentence by sentence and when the sentence specifies a "what" (e.g., "syntax should be consistent ...", "user should be able to specify a range of locations ..."), determine if the program satisfies the "what". Volume Volume testing is subjecting the program to heavy volumes of data. For instance, a compiler would be fed an absurdly large source program to compile. A linkage editor might be fed a program containing thousands of modules. An operating system's job queue would be filled to capacity. In other words, the purpose of volume testing is to show that the program cannot handle the volume of data specified in its requirements. Usability Usability testing is an attempt to find human-factor, or usability problems. Unfortunately, since the computing industry has placed insufficient attention on studying and defining good human-factor considerations of programming systems, an analysis of human factors is still a highly subjective matter. 3.2 FORMS GENERATOR ACCEPTANCE/PREOPERATING PROCEDURES The following paragraphs explain the necessary preparations and procedures for acceptance testing of the Forms Generator. 3.3 EQUIPMENT PREPARATION In order to complete acceptance testing, the Forms Generator must be available on a Data General MV 10000 running under AOS/VS. 3.4 DIGITAL PROCESSOR PREPARATION In order to complete acceptance testing, the ROLM/Data General Ada Development Environment (ADE) must be available. 3.5 TESTING PROCEDURE The procedure for acceptance testing is to fulfill all the test specifications in Appendix A. This can be accomplished by completing the second and third steps from Section 3.1. As noted in step 2, input files for the Forms Generator must be created to satisfy all of the test specifications in Appendix A. In addition, the expected output forms for the Forms Generator must be created based on the input files. Then, 3-2 TESTING REQUIREMENTS when the Forms Generator tool is ready to undergo acceptance testing, step 3 is started. Thus, the input files are executed with the tool. The output files that are generated are compared with the expected output files, which have already been established as correct. The file names for the test data library and the corresponding test specifications that are satisfied need to be documented in the Test Data Matrix in Appendix C. Finally, the results of testing are analyzed and the Test Specification Matrix in Appendix B is updated. NOTE One Ada source program and corresponding keystroke file may be used to satisfy a number of test specifications in Appendix A. In other words, it is not necessary to create a separate set of input files for each test specification in Appendix A. 3-3 CHAPTER 4 TEST MANAGEMENT The Forms Generator development team is responsible for management of the testing described in this document. The Forms Generator development team responsibilities are to: o create test data according to the test specifications in Appendix A, and record the test data information in the Test Data Matrix in Appendix B, o conduct the test procedures described in the Testing Requirements section, o maintain the Test Specifications Matrix in Appendix B, and o write an internal test report. 4-1 CHAPTER 5 PERSONNEL REQUIREMENTS The software development team for the Forms Generator is the only personnel required to complete the acceptance testing described in this document. 5-1 CHAPTER 6 HARDWARE REQUIREMENTS The acceptance testing described in this document shall be conducted on a Data General MV 10000 running under AOS/VS. If automated testing of the interactive tools is to be performed (as opposed to manual testing), Input/Output redirection is required. AOS/VS does not provide this. At the customer's discretion, NOSC-TECR (using EUNICE) may be used to perform automated testing of the interactive aspects of the tools. 6-1 CHAPTER 7 SOFTWARE REQUIREMENTS The acceptance testing described in this document requires the ROLM/Data General Ada Development Environment (ADE). If automated testing of the interactive tools is to be performed (as opposed to manual testing), Input/Output redirection is required. AOS/VS does not provide this. At the customer's discretion, NOSC-TECR (using EUNICE) may be used to perform automated testing of the interactive aspects of the tools. 7-1 CHAPTER 8 TESTING SCHEDULE The acceptance testing described in this document will take 1-2 weeks to complete. 8-1 CHAPTER 9 QUALITY ASSURANCE ACSL personnel will be responsible for the following Quality Assurance and Configuration Management tasks: o verifying that the test data satisfies the test specifications, o verifying that the documentation of each test is complete, and o maintaining configuration control of all software undergoing test. 9-1 APPENDIX A TEST SPECIFICATIONS This appendix contains the test specifications for the Forms Generator System. Each test specification includes a list of the requirements that are satisfied, a description of the test, assumptions for the test, and a test synopsis. The test synopsis describes the input and expected results for the test. The test categories that are used for each test specification are also provided in the synopsis. A description of the various test categories is provided in the Testing Requirements section. There are three distinct features of the Forms Generator System that are exercised by the tests described in this document: * Interactive Forms Generator * Batch Forms Generator * Forms Executor The Interactive Forms Generator is exercised in test sets 1 to 8. These tests are highly terminal interactive and require much in the way of tester activity unless I/O redirection is employed to input the tester's keystrokes. As a side effect of these tests, the Forms Executor, which is employed heavily by the Interactive Forms Generator, is exercised by these tests. The Batch Forms Generator is exercised in test set 9. Command and data files do most of the work of the test, and the tester's role is primarily to invoke the required commands to perform the tests. The Forms Executor is exercised in test set 10. These tests are moderately terminal interactive and also employ the use of simple commands (invocations of the Ada compiler, for instance). The tester's keystrokes may be provided by a data file if I/O redirection is supported on the system on which the tests are being run. A-1 TEST SPECIFICATIONS A.1 CREATE/LOAD FORM A.1.1 REQUIREMENTS MET BY TEST 5 (see Appendix C) A.1.2 DESCRIPTION OF TEST The tester will invoke the Interactive Form Generator and select either menu option 1 (Create a Form) or menu option 2 (Load a Form). He will then provide the inputs listed under Test Synopsis (below) and observe/record the results. After providing all inputs, he will selection menu option 6 (Exit) and return to the operating system. These two menu options are combined into this one test because they both involve loading in a form. A.1.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Interactive Form Generator. The tester knows how to use the IFG and knows the commands associated with it. A.1.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Select option 1; Blank form is FACILITY strike RETURN key loaded 2 Exit the Edit, and Blank form is FACILITY select option 2; displayed strike any key except for the RETURN key; select option 3 3 Exit the Edit; and Form is loaded FACILITY select option 2; strike the RETURN key; enter valid file name for existing form 4 Exit the Edit; and Form was not FACILITY select option 1; cleared strike any key except A-2 TEST SPECIFICATIONS for the RETURN key; select option 3 (edit) 5 Exit the Edit; and Blank form is FACILITY select option 1; loaded enter RETURN key; enter another RETURN 6 Select option 6 (exit); No unrecoverable FACILITY strike RETURN key; errors reinvoke IFG program; select option 2; enter a valid directory reference with the name of an existing form file 7 Exit the Edit; select No unrecoverable FACILITY option 2; enter the errors RETURN key; enter a valid directory reference with the name of a file that exists but is not a valid form file 8 Select option 2; No unrecoverable FACILITY enter a valid errors directory reference with the name of a file that does not exist 9 Select option 2; No unrecoverable FACILITY enter an invalid error directory reference with the name of a file that exists 10 Select option 2; No unrecoverable FACILITY enter an invalid errors directory reference with the name of a file that does not exist 11 Select option 2; No unrecoverable FACILITY enter an invalid errors file name 12 Select option 6 (exit) Cleanup for next FACILITY test A-3 TEST SPECIFICATIONS A.2 EDIT FORM 1 A.2.1 REQUIREMENTS MET BY TEST 1, 3, 4, 5, 6, 7 (see Appendix C) A.2.2 DESCRIPTION OF TEST The tester will invoke the Interactive Form Generator and select menu option 3 (Edit a Form). He will then provide the inputs listed under Test Synopsis (below) and observe/record the results. A.2.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Interactive Form Generator. The tester knows how to use the IFG and knows the commands associated with it. A.2.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. These tests must be conducted in the sequence shown (test 1 before test 2, test 2 before test 3, etc). INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Invoke the IFG; select No unrecoverable FACILITY option 3 errors 2 Select option 1; Blank form is FACILITY strike the RETURN displayed key; enter another RETURN 3 Use the arrow keys to Cursor Movement FACILITY move about on the is correct screen; try as a minimum moving up from HOME, left from HOME, down from the lower right-hand corner, right from the lower right-hand corner, left from the lower left-hand corner, down from the lower left-hand A-4 TEST SPECIFICATIONS corner, right from the upper right-hand corner, up from the upper right-hand corner, and across line boundaries (left and right) over the form 4 Exit the Edit, select option 2; Test file is FACILITY enter the RETURN key; displayed and load the first EDIT FORM test file 5 Copy the first field to after Copy a Field FACILITY the last field; copy this last (A.2.1) field to somewhere in the middle of the form; try to copy one field on top of another; perform at least 5 more copy operations of your choice; use both forms of the Copy a Field command (ie, keystroke and command line) 6 Copy the last line in the form Copy a Line FACILITY to before the first line; copy (A.2.2) the first line in the form to before the last line; perform at least 5 more copy line operations of your choice; use both forms of the Copy a Line command 7 Exit the Edit; select option Cleanup for FACILITY 6; and do not save the form next test A-5 TEST SPECIFICATIONS A.3 EDIT FORM 2 A.3.1 REQUIREMENTS MET BY TEST 1, 3, 4, 5, 6, 7 (see Appendix C) A.3.2 DESCRIPTION OF TEST The tester will invoke the Interactive Form Generator and select menu option 3 (Edit a Form). He will then provide the inputs listed under Test Synopsis (below) and observe/record the results. A.3.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Interactive Form Generator. The tester knows how to use the IFG and knows the commands associated with it. A.3.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. These tests must be conducted in the sequence shown (test 1 before test 2, test 2 before test 3, etc). INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Select option 2 and Test file is FACILITY load the first EDIT displayed FORM test file 2 Create four new fields, Create a New FACILITY each of a different Field (A.2.3) code (a,b,n,x) 3 Try to create a field Field not FACILITY on top of an created existing field 4 Try to create a field Field not FACILITY that overlaps into created the next field 5 Try at least 5 more Create a New FACILITY fields on the form Field 6 Delete characters at Delete Char FACILITY random; try to delete (A.2.4) chars within a field; A-6 TEST SPECIFICATIONS delete the first character in the form; delete the last char in the form 7 Delete the first field Delete Field FACILITY on the form; delete (A.2.5) the last field on the form; try to delete a field when the cursor is not resting in a field 8 Delete the first line Delete Line FACILITY of the form; delete (A.2.6) the last line of the form; try to delete a line with a field in it; delete a line which does not have a field in it 9 Invoke the Help display Help (A.2.7) FACILITY 10 Exit the Help; Exit Cleanup FACILITY the Edit; enter a RETURN; and do not save the form A-7 TEST SPECIFICATIONS A.4 EDIT FORM 3 A.4.1 REQUIREMENTS MET BY TEST 1, 3, 4, 5, 6, 7 (see Appendix C) A.4.2 DESCRIPTION OF TEST The tester will invoke the Interactive Form Generator and select menu option 3 (Edit a Form). He will then provide the inputs listed under Test Synopsis (below) and observe/record the results. A.4.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Interactive Form Generator. The tester knows how to use the IFG and knows the commands associated with it. A.4.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. These tests must be conducted in the sequence shown (test 1 before test 2, test 2 before test 3, etc). INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Select option 2 and Test file is FACILITY load the first EDIT displayed FORM test file 2 Insert a char from Insert Char FACILITY HOME positon; (A.2.8) insert a char from lower right-hand corner; insert 5 chars at random; try to insert a char from within a field 3 Insert a blank line Insert Line FACILITY before the first (A.2.9) line; insert a blank line before the last line; insert a blank line around the middle of the form; insert A-8 TEST SPECIFICATIONS a blank line when there is text or one or more fields on the last line 4 Position to an existing Modify Field FACILITY field; perform 10 (A.2.10) modifies on it; change the modes to a,n,b,x in 4 of the modifies; overlap with the next field in one of the modifies; use both types of renditions; one modify should have no initial field value 5 Exit the Edit; enter a Cleanup FACILITY RETURN; and do not save the form A-9 TEST SPECIFICATIONS A.5 EDIT FORM 4 A.5.1 REQUIREMENTS MET BY TEST 1, 3, 4, 5, 6, 7 (see Appendix C) A.5.2 DESCRIPTION OF TEST The tester will invoke the Interactive Form Generator and select menu option 3 (Edit a Form). He will then provide the inputs listed under Test Synopsis (below) and observe/record the results. A.5.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Interactive Form Generator. The tester knows how to use the IFG and knows the commands associated with it. A.5.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. These tests must be conducted in the sequence shown (test 1 before test 2, test 2 before test 3, etc). INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Select option 2 and Test file is FACILITY load the first EDIT displayed FORM test file 2 Move the first field Move Field FACILITY to after the last (A.2.11) field; move the last field to before the first field; perform 5 other moves; try to move a field into another field 3 Move the first line Move Line FACILITY to before the last (A.2.12) line; move the last line to before the first line; perform 3 more moves 4 Rubout the first and Rubout Char FACILITY A-10 TEST SPECIFICATIONS last chars; rubout (A.2.13) chars at random; try to rubout a char in a field 5 Exit the Edit; enter Cleanup FACILITY a RETURN; and do not save the form A-11 TEST SPECIFICATIONS A.6 MODIFY FORM A.6.1 REQUIREMENTS MET BY TEST 1, 3, 4, 6 (see Appendix C) A.6.2 DESCRIPTION OF TEST The tester will invoke the Interactive Form Generator and select menu option 4 (Modify a Form). He will then provide the inputs listed under Test Synopsis (below) and observe/record the results. After providing all inputs, he will selection menu option 6 (Exit) and return to the operating system. A.6.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Interactive Form Generator. The tester knows how to use the IFG and knows the commands associated with it. A.6.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Select option 2 and Test file is FACILITY load the first EDIT displayed FORM test file; Exit the Edit 2 Select option 4; Modify Options FACILITY examine current (A.3) form options; enter a RETURN 3 Vary the form size, Form Attributes FACILITY form position, and modified clear screen options; return to Main Menu by entering a RETURN 4 Repeat steps 2 and 3 Form Attributes FACILITY several times, and modified include at least the following tests: clear screen YES and NO, form position at A-12 TEST SPECIFICATIONS home and lower right- hand corner, form position around the middle of the screen, form size=screen size, form size < screen size, form size > screen size; return to Main Menu by entering a RETURN 5 Exit the IFG via option 6 Cleanup FACILITY and do not save form A-13 TEST SPECIFICATIONS A.7 SAVE FORM A.7.1 REQUIREMENTS MET BY TEST 1, 4 (see Appendix C) A.7.2 DESCRIPTION OF TEST The tester will invoke the Interactive Form Generator and select inputs listed under Test Synopsis (below) and observe/record the results. After providing all inputs, he will selection menu option 6 (Exit) and return to the operating system. A.7.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Interactive Form Generator. The tester knows how to use the IFG and knows the commands associated with it. A.7.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Select option 2; enter Form is loaded FACILITY valid file name for existing form; exit the Edit 2 Select option 5; strike Current form is FACILITY RETURN key saved in the original file 3 Select option 5 and Current form is FACILITY enter another file saved in name another file 4 Select option 5 Current form is FACILITY and enter another saved directory reference and file name 5 Select option 5 Current form is FACILITY and enter invalid NOT saved file name A-14 TEST SPECIFICATIONS 6 Select option 5 Current form is FACILITY and enter invalid NOT saved directory reference and file name 7 Select option 6 Cleanup FACILITY and exit with no save A-15 TEST SPECIFICATIONS A.8 EXIT INTERACTIVE FORM GENERATOR A.8.1 REQUIREMENTS MET BY TEST 1 (see Appendix C) A.8.2 DESCRIPTION OF TEST The tester will invoke the Interactive Form Generator and select inputs listed under Test Synopsis (below) and observe/record the results. After providing all inputs, he will selection menu option 6 (Exit) and return to the operating system. A.8.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Interactive Form Generator. The tester knows how to use the IFG and knows the commands associated with it. A.8.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Select option 2; enter Form is loaded FACILITY valid file name for existing form 2 Exit the Edit; Current form is FACILITY Select option 5; saved strike RETURN key 3 Select option 6 Exit without FACILITY prompt 4 Enter IFG, select opt Form is loaded FACILITY 1, enter RETURN as blank (blank form) 5 Exit the Edit; Form is still FACILITY Select option 6; loaded, and strike any character exit does not except for RETURN happen. key 6 Select option 6; Exit FACILITY A-16 TEST SPECIFICATIONS strike the RETURN key 7 Try several "normal" General tests FACILITY runs of the IFG, saving the forms each time; at least one edit of a blank form, one edit of an old form, and one load of a non- existant form should be done with exits (opt 5) done each time to see that proper prompts appear A-17 TEST SPECIFICATIONS A.9 BATCH FORMS GENERATOR A.9.1 REQUIREMENTS MET BY TEST 1, 4, 6, 7 (Appendix C) A.9.2 DESCRIPTION OF TEST The tester will invoke the Batch Forms Generator and provide input data files to the program. Outputs, including error messages, generated by the program will be observed. A.9.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Batch Forms Generator (BFG). The tester knows how to use the BFG and knows the commands associated with it. A.9.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Invoke BFG; present Normal operation FACILITY name of test file 1; with possible observe results message generation and note discrepancies 2 Invoke BFG; present BFG recovers FACILITY invalid file name 3 Invoke BFG; present BFG recovers FACILITY invalid dir name 4 Invoke BFG; present Normal operation FACILITY name of test file 2; with possible observe results and message generation not discrepancies 5 Invoke BFG; present Normal operation FACILITY name of test file 3; with possible observe results and message generation not discrepancies 6 Invoke BFG; present Normal operation FACILITY name of test file 4; with possible observe results and message generation A-18 TEST SPECIFICATIONS not discrepancies 7 Invoke BFG; present Normal operation FACILITY name of test file 5; with possible observe results and message generation not discrepancies A-19 TEST SPECIFICATIONS A.10 FORM EXECUTOR A.10.1 REQUIREMENTS MET BY TEST 1, 2, 3, 8 (see Appendix C) A.10.2 DESCRIPTION OF TEST The tester will compile and execute a group of test programs. These programs WITH in the Form Executor package and use it to manipulate forms. The tester will provide information to the displayed forms, manipulate the cursor, test the field data inputs, etc, and observe the results. A.10.3 ASSUMPTIONS The tester knows the basics of using the host computer's operating system and knows how to invoke the Ada compiler on the host computer and run programs compiled by this Ada compiler. The tester knows how to provide input to forms presented by the Forms Executor. A.10.4 TEST SYNOPSIS The following table summarizes the test data, expected outputs, and test categories addressed by the associated test data. Tests 1 and 2 are performed on one type of terminal, tests 3 and 4 on another, and tests 5 and 6 on yet another. INDEX INPUT DATA EXPECTED RESULTS CATEGORIES ===== ========== ================ ========== 1 Compile test program 1; Successful test FACILITY execute it; provide inputs to the form; test for invalid inputs (such as alphabetic data in a numeric field, etc) 2 Compile test program 2; Successful test FACILITY execute it; provide inputs to the form; test for invalid inputs (such as alphabetic data in a numeric field, etc) 3 Compile test program 3; Successful test FACILITY execute it; provide inputs to the form; test for invalid A-20 TEST SPECIFICATIONS inputs (such as alphabetic data in a numeric field, etc); do this test on a different type of terminal than tests 1 and 2 4 Compile test program 4; Successful test FACILITY execute it; provide inputs to the form; test for invalid inputs (such as alphabetic data in a numeric field, etc) 5 Compile test program 5; Successful test FACILITY execute it; provide inputs to the form; test for invalid inputs (such as alphabetic data in a numeric field, etc); do this test on a different type of terminal than tests 1, 2, 3, and 4 6 Compile test program 6; Successful test FACILITY execute it; provide inputs to the form; test for invalid inputs (such as alphabetic data in a numeric field, etc) A-21 APPENDIX B CROSS-REFERENCE MATRICES B.1 TEST/REQUIREMENTS MATRIX ----------------------------------------------------------------------- | TEST SPEC | REQUIREMENTS | CHECK | COMMENTS | |===========|==============|=======|==================================| | 1 | 5 | | | |-----------|--------------|-------|----------------------------------| | 2 | 1,3,4,5,6,7 | | | |-----------|--------------|-------|----------------------------------| | 3 | 1,3,4,5,6,7 | | | |-----------|--------------|-------|----------------------------------| | 4 | 1,3,4,5,6,7 | | | |-----------|--------------|-------|----------------------------------| | 5 | 1,3,4,5,6,7 | | | |-----------|--------------|-------|----------------------------------| | 6 | 1,3,4,6 | | | |-----------|--------------|-------|----------------------------------| | 7 | 1,4 | | | |-----------|--------------|-------|----------------------------------| | 8 | 1 | | | |-----------|--------------|-------|----------------------------------| | 9 | 1,4,6,7 | | | |-----------|--------------|-------|----------------------------------| | 10 | 1,2,3,8 | | | |-----------|--------------|-------|----------------------------------| B-1 CROSS-REFERENCE MATRICES B.2 REQUIREMENTS/TEST MATRIX TEST SPEC REQUIREMENT AND PROPOSAL SECTION 2,3,4, 1 Page 2-2, Section 3.2.3, A form is a collection of 5,6,7, screen formats, their components and attributes. 8,9,10 It consists of a rectangular region of a single formatted screen the same width as a physical display. 10 2 Page 2-2, Section 3.2.2, A form can be redesigned or installed on a different terminal without affecting the application. The application is also relieved of handling simple input edit errors. 2,3,4, 3 Page 2-2, Section 3.2.2, Interactions with the 5,6,10 terminal are shifted from the application program to the Form Executor. 2,3,4, 4 Page 2-2, Section 3.2.1, Screen Generator will 5,6,7,9 translate a textual description of a virtual terminal screen format into a structure which is machine readable. 1,2,3, 5 Page 2-2, Section 3.2.4, User Interface Form 4,5 Generator will provide an interactive interface to design a screen format and save the representation in a machine readable structure. 2,3,4, 6 Page 2-2, Section 3.2.3, A form is described by 5,6,9 the values of the following attributes: 1. Size - the number of rows and columns in form 2. Position - the position on the physical screen of the upper leftmost position of the form when it is displayed 3. Clear Screen - indicates whether the entire physical screen is to be cleared before the form is displayed 2,3,4, 7 Page 2-3, Section 3.2.3, The fields of a form are 5,9 described by the values of these attributes: 1. Name - an arbitrary character string that uniquely identifies the field within a form 2. Position - the row and column within the B-2 CROSS-REFERENCE MATRICES form at which the first character of the field is located 3. Length - the number of characters in the field 4. Graphic Rendition - the graphic rendition of the characters in the field 5. Character Limitation - the characters that are permitted to be entered into a field 6. Value - the initial value of the field when it is displayed 7. Mode - indicates whether the field may be modified during program execution 10 8 Page 2-3, Section 3.2.2, The Form Executor will provide procedural and functional interfaces that enable a program to access the output of the Screen Generator or User Interface Form Generator programs and present it to a physical terminal. The following operations are provided: 1. Access Form - the location of a form is specified and the form is made available to the program 2. Modify Field - the value of a field is changed (if permitted) 3. Present Form - the form is displayed on the physical screen and the terminal user is permitted to modify those portions of the form identified as being modifiable 4. Query Form - determine information about the form after the terminal user has entered all data B-3 CROSS-REFERENCE MATRICES B.3 TEST FILE MATRIX ------------------------------------------------------------------ | TEST FILE NAME | TEST SPECIFICATION(S) SATISFIED | |==================|=============================================| | | | |------------------|---------------------------------------------| | | | |------------------|---------------------------------------------| | | | |------------------|---------------------------------------------| | | | |------------------|---------------------------------------------| | | | |------------------|---------------------------------------------| | | | |------------------|---------------------------------------------| | | | |------------------|---------------------------------------------| | | | |------------------|---------------------------------------------| B-4 APPENDIX C GLOSSARY __________ ____ 1. Acceptance Test An acceptance test is a test conducted by a customer to determine if the software or system contracted for is performing as stated in the contractual requirements. ____ 2. ACSL Advanced Computer Systems Laboratory, Texas Instruments. ________ ____ 3. Facility Test Facility testing is the determination of whether each facility or function is actually implemented. The procedure is to scan the requirements sentence by sentence and when the sentence specifies a "what" (e.g., "syntax should be consistent ...", "user should be able to specify a range of locations ..."), determine if the program satisfies the "what". ____ 4. NOSC Naval Ocean Systems Center. _________ ____ 5. Usability Test Usability testing is an attempt to find human-factor, or usability problems. Unfortunately, since the computing industry has placed insufficient attention on studying and defining good human-factor considerations of programming systems, an analysis of human factors is still a highly subjective matter. ______ ____ 6. Volume Test Volume testing is subjecting the program to heavy volumes of data. For instance, a compiler would be fed an absurdly large source program to compile. A linkage editor might be fed a program containing thousands of modules. An operating system's job queue would be filled to capacity. In other words, the purpose of volume testing is to show that the program cannot handle the volume of data specified in its requirements. C-1