Programmer's ROM - The Computer Language Library

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

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

Wrap

Text File | 1988-05-03 | 172.3 KB | 6,380 lines

||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| Computer Program Test Procedures for a ANSI X3.64 Compatible Virtual Terminal in Ada Prepared for: ||||||||||||||||||||||||| ||||||||||||||||||||||||| Advanced Computer Systems Lab ||||||||||||||||||||||||| Texas Instruments ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| Equipment Group - ACSL ||||||||||||||||||||||||| P.O. Box 801, M.S. 8007 ||||||||||||||||||||||||| McKinney, Texas 75069 ||||||||||||||||||||||||| XX December 1984 ||||||||||||||||||||||||| ||||||||||||||||||||||||| TEXAS INSTRUMENTS INCORPORATED ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| ||||||||||||||||||||||||| CONTENTS CHAPTER 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . 1-1 PURPOSE . . . . . . . . . . . . . . . . . . . . . 1-1 SCOPE . . . . . . . . . . . . . . . . . . . . . . 1-1 SUMMARY . . . . . . . . . . . . . . . . . . . . . 1-1 CHAPTER 2 APPLICABLE DOCUMENTS . . . . . . . . . . . . . . . 2-1 CHAPTER 3 TESTING REQUIREMENTS . . . . . . . . . . . . . . . 3-1 GENERAL . . . . . . . . . . . . . . . . . . . . . 3-1 VIRTUAL TERMINAL ACCEPTANCE/PREOPERATING PROCEDURES . . . . . . . . . . . . . . . . . . . . 3-2 EQUIPMENT PREPARATION . . . . . . . . . . . . . 3-2 DIGITAL PROCESSOR PREPARATION . . . . . . . . . 3-2 TESTING PROCEDURE . . . . . . . . . . . . . . . 3-3 TESTING SETTING TAB STOPS . . . . . . . . . . . 3-4 Contents Of The Test . . . . . . . . . . . . . . 3-4 Description Of The Actual Display . . . . . . . 3-4 TESTING CLEARING TAB STOPS . . . . . . . . . . . 3-5 Contents Of The Test . . . . . . . . . . . . . . 3-5 Description Of The Actual Display . . . . . . . 3-5 TESTING MOVING BY TAB STOPS . . . . . . . . . . 3-6 Contents Of The Test . . . . . . . . . . . . . . 3-6 Description Of The Actual Display . . . . . . . 3-6 TESTING MOVING TO A NEW LINE . . . . . . . . . . 3-7 Contents Of The Test . . . . . . . . . . . . . . 3-7 Description Of The Actual Display . . . . . . . 3-7 TESTING MOVING TO A NEW PAGE . . . . . . . . . . 3-8 Contents Of The Test . . . . . . . . . . . . . . 3-8 Description Of The Actual Display . . . . . . . 3-8 TESTING WRITING CHARACTERS AND STRINGS TO THE DISPLAY . . . . . . . . . . . . . . . . . . . . 3-9 Contents Of The Test . . . . . . . . . . . . . . 3-9 Description Of The Actual Display . . . . . . . 3-9 TESTING READING CHARACTERS AND STRINGS FROM THE KEYBOARD . . . . . . . . . . . . . . . . . . . 3-10 Contents Of The Test . . . . . . . . . . . . . 3-10 Description Of The Actual Display . . . . . . 3-11 TESTING RINGING THE TERMINAL'S BELL . . . . . 3-12 Contents Of The Test . . . . . . . . . . . . . 3-12 Description Of The Actual Display . . . . . . 3-12 TESTING SETTING TAB STOPS . . . . . . . . . . 3-13 Contents Of The Test . . . . . . . . . . . . . 3-13 Description Of The Actual Display . . . . . . 3-13 Page 2 TESTING CLEARING TAB STOPS . . . . . . . . . . 3-14 Contents Of The Test . . . . . . . . . . . . . 3-14 Description Of The Actual Display . . . . . . 3-14 TESTING MOVING TO A TAB STOP . . . . . . . . . 3-15 Contents Of The Test . . . . . . . . . . . . . 3-15 Description Of The Actual Display . . . . . . 3-15 TESTING MOVING TO A NEW LINE . . . . . . . . . 3-16 Contents Of The Test . . . . . . . . . . . . . 3-16 Description Of The Actual Display . . . . . . 3-16 TESTING MOVING TO A NEW PAGE . . . . . . . . . 3-17 Contents Of The Test . . . . . . . . . . . . . 3-17 Description Of The Actual Display . . . . . . 3-17 TESTING WRITING CHARACTERS AND STRINGS TO THE DISPLAY . . . . . . . . . . . . . . . . . . . 3-18 Contents Of The Test . . . . . . . . . . . . . 3-18 Description Of The Actual Display . . . . . . 3-18 TESTING READING CHARACTERS AND STRINGS FROM THE KEYBOARD . . . . . . . . . . . . . . . . . . . 3-19 Contents Of The Test . . . . . . . . . . . . . 3-19 Description Of The Actual Display . . . . . . 3-20 TESTING RINGING THE TERMINAL'S BELL . . . . . 3-21 Contents Of The Test . . . . . . . . . . . . . 3-21 Description Of The Actual Display . . . . . . 3-21 TESTING DELETING CHARACTERS FROM THE DISPLAY . 3-22 Contents Of The Test . . . . . . . . . . . . . 3-22 Description Of The Actual Display . . . . . . 3-22 TESTING DELETING LINES FROM THE DISPLAY . . . 3-23 Contents Of The Test . . . . . . . . . . . . . 3-23 Description Of The Actual Display . . . . . . 3-23 TESTING ERASING CHARACTERS FROM THE DISPLAY . 3-24 Contents Of The Test . . . . . . . . . . . . . 3-24 Description Of The Actual Display . . . . . . 3-25 TESTING ERASING BETWEEN SPECIFIC POSITIONS ON THE DISPLAY . . . . . . . . . . . . . . . . . 3-26 Contents Of The Test . . . . . . . . . . . . . 3-26 Description Of The Actual Display . . . . . . 3-27 TESTING INSERTING CHARACTERS ONTO THE DISPLAY 3-28 Contents Of The Test . . . . . . . . . . . . . 3-28 Description Of The Actual Display . . . . . . 3-29 TESTING INSERTING LINES ONTO THE DISPLAY . . . 3-30 Contents Of The Test . . . . . . . . . . . . . 3-30 Description Of The Actual Display . . . . . . 3-30 TESTING SETTING THE GRAPHIC RENDITION ON THE DISPLAY . . . . . . . . . . . . . . . . . . . 3-31 Contents Of The Test . . . . . . . . . . . . . 3-31 Description Of The Actual Display . . . . . . 3-31 TESTING DEFINING QUALIFIED AREAS ON THE DISPLAY 3-32 Contents Of The Test . . . . . . . . . . . . . 3-32 What The Tester Has To Type . . . . . . . . . 3-32 Description Of The Actual Display . . . . . . 3-32 TESTING CLEARING QUALIFIED AREAS ON THE DISPLAY 3-33 Contents Of The Test . . . . . . . . . . . . . 3-33 What The Tester Needs To Type . . . . . . . . 3-33 Description Of The Actual Display . . . . . . 3-34 TESTING MOVING BY TAB STOPS ON THE DISPLAY . . 3-35 Page 3 Contents Of The Test . . . . . . . . . . . . . 3-35 What The Tester Needs To Type . . . . . . . . 3-35 Description Of The Actual Display . . . . . . 3-36 TESTING ERASING BETWEEN SPECIFIED POSITIONS ON THE DISPLAY . . . . . . . . . . . . . . . . . 3-37 Contents Of The Test . . . . . . . . . . . . . 3-37 What The Tester Needs To Type . . . . . . . . 3-37 Description Of The Actual Display . . . . . . 3-38 TESTING READING CHARACTERS AND STRINGS FROM THE DISPLAY BUFFER . . . . . . . . . . . . . . . . 3-39 Contents Of The Test . . . . . . . . . . . . . 3-39 What The Tester Needs To Type . . . . . . . . 3-39 Description Of The Actual Display . . . . . . 3-40 TESTING WRITING CHARACTERS AND STRINGS TO THE DISPLAY BUFFER . . . . . . . . . . . . . . . . 3-41 Contents Of The Test . . . . . . . . . . . . . 3-41 What The Tester Needs To Type . . . . . . . . 3-41 Description Of The Actual Display . . . . . . 3-41 TESTING ACTIVATING A FORM FOR USER FILL IN . . 3-42 Contents Of The Test . . . . . . . . . . . . . 3-42 What The Tester Needs To Type . . . . . . . . 3-42 Description Of The Actual Display . . . . . . 3-43 CHAPTER 4 TEST MANAGEMENT . . . . . . . . . . . . . . . . . 4-1 CHAPTER 5 PERSONNEL REQUIREMENTS . . . . . . . . . . . . . . 5-1 CHAPTER 6 HARDWARE REQUIREMENTS . . . . . . . . . . . . . . 6-1 CHAPTER 7 SOFTWARE REQUIREMENTS . . . . . . . . . . . . . . 7-1 CHAPTER 8 TESTING SCHEDULE . . . . . . . . . . . . . . . . . 8-1 CHAPTER 9 QUALITY ASSURANCE . . . . . . . . . . . . . . . . 9-1 Page 4 APPENDIX A TEST SPECIFICATIONS SET_TAB . . . . . . . . . . . . . . . . . . . . . A-2 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-2 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-2 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-2 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-2 CLEAR_TAB . . . . . . . . . . . . . . . . . . . . A-3 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-3 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-3 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-3 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-3 TAB . . . . . . . . . . . . . . . . . . . . . . . A-4 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-4 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-4 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-4 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-4 NEW_LINE . . . . . . . . . . . . . . . . . . . . . A-5 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-5 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-5 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-5 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-5 NEW_PAGE . . . . . . . . . . . . . . . . . . . . . A-6 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-6 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-6 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-6 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-6 PUT . . . . . . . . . . . . . . . . . . . . . . . A-7 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-7 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-7 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-7 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-7 GET . . . . . . . . . . . . . . . . . . . . . . . A-9 REQUIREMENTS MET BY TEST . . . . . . . . . . . . A-9 DESCRIPTION OF TEST . . . . . . . . . . . . . . A-9 ASSUMPTIONS . . . . . . . . . . . . . . . . . . A-9 TEST SYNOPSIS . . . . . . . . . . . . . . . . . A-9 BELL . . . . . . . . . . . . . . . . . . . . . . A-11 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-11 DESCRIPTION OF TEST . . . . . . . . . . . . . A-11 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-11 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-11 SET_TAB . . . . . . . . . . . . . . . . . . . . A-12 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-12 DESCRIPTION OF TEST . . . . . . . . . . . . . A-12 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-12 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-12 CLEAR_TAB . . . . . . . . . . . . . . . . . . . A-13 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-13 DESCRIPTION OF TEST . . . . . . . . . . . . . A-13 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-13 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-13 TAB . . . . . . . . . . . . . . . . . . . . . . A-14 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-14 DESCRIPTION OF TEST . . . . . . . . . . . . . A-14 Page 5 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-14 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-14 NEW_LINE . . . . . . . . . . . . . . . . . . . . A-15 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-15 DESCRIPTION OF TEST . . . . . . . . . . . . . A-15 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-15 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-15 NEW_PAGE . . . . . . . . . . . . . . . . . . . . A-16 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-16 DESCRIPTION OF TEST . . . . . . . . . . . . . A-16 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-16 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-16 PUT . . . . . . . . . . . . . . . . . . . . . . A-17 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-17 DESCRIPTION OF TEST . . . . . . . . . . . . . A-17 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-17 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-17 GET . . . . . . . . . . . . . . . . . . . . . . A-19 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-19 DESCRIPTION OF TEST . . . . . . . . . . . . . A-19 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-19 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-19 DELETE_CHARACTER . . . . . . . . . . . . . . . . A-21 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-21 DESCRIPTION OF TEST . . . . . . . . . . . . . A-21 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-21 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-21 DELETE_LINE . . . . . . . . . . . . . . . . . . A-23 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-23 DESCRIPTION OF TEST . . . . . . . . . . . . . A-23 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-23 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-23 ERASE_IN_DISPLAY . . . . . . . . . . . . . . . . A-25 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-25 DESCRIPTION OF TEST . . . . . . . . . . . . . A-25 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-25 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-25 ERASE_IN_LINE . . . . . . . . . . . . . . . . . A-27 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-27 DESCRIPTION OF TEST . . . . . . . . . . . . . A-27 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-27 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-27 INSERT CHARACTERS . . . . . . . . . . . . . . . A-29 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-29 DESCRIPTION OF TEST . . . . . . . . . . . . . A-29 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-29 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-29 INSERT_LINE . . . . . . . . . . . . . . . . . . A-31 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-31 DESCRIPTION OF TEST . . . . . . . . . . . . . A-31 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-31 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-31 SELECT_GRAPHIC_RENDITION . . . . . . . . . . . . A-33 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-33 DESCRIPTION OF TEST . . . . . . . . . . . . . A-33 Page 6 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-33 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-33 BELL . . . . . . . . . . . . . . . . . . . . . . A-34 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-34 DESCRIPTION OF TEST . . . . . . . . . . . . . A-34 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-34 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-34 DEFINE_QUALIFIED_AREAS . . . . . . . . . . . . . A-35 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-35 DESCRIPTION OF TEST . . . . . . . . . . . . . A-35 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-35 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-35 CLEAR_QUALIFIED_AREAS . . . . . . . . . . . . . A-36 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-36 DESCRIPTION OF TEST . . . . . . . . . . . . . A-36 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-36 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-36 TAB . . . . . . . . . . . . . . . . . . . . . . A-37 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-37 DESCRIPTION OF TEST . . . . . . . . . . . . . A-37 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-37 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-37 GET . . . . . . . . . . . . . . . . . . . . . . A-38 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-38 DESCRIPTION OF TEST . . . . . . . . . . . . . A-38 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-38 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-38 ERASE_AREA . . . . . . . . . . . . . . . . . . . A-39 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-39 DESCRIPTION OF TEST . . . . . . . . . . . . . A-39 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-39 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-39 ERASE_DISPLAY . . . . . . . . . . . . . . . . . A-40 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-40 DESCRIPTION OF TEST . . . . . . . . . . . . . A-40 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-40 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-40 ACTIVATE_FORM . . . . . . . . . . . . . . . . . A-41 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-41 DESCRIPTION OF TEST . . . . . . . . . . . . . A-41 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-41 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-41 PUT . . . . . . . . . . . . . . . . . . . . . . A-43 REQUIREMENTS MET BY TEST . . . . . . . . . . . A-43 DESCRIPTION OF TEST . . . . . . . . . . . . . A-43 ASSUMPTIONS . . . . . . . . . . . . . . . . . A-43 TEST SYNOPSIS . . . . . . . . . . . . . . . . A-43 APPENDIX B MATRICES Page 7 APPENDIX C GLOSSARY CHAPTER 1 1.1 INTRODUCTION 1.2 PURPOSE This Computer Program Test Procedures document describes the acceptance test procedures for the ANSI X3.64 Compatible Virtual Terminal computer program. This research and development is being done for the Naval Ocean Systems Center (NOSC) under contract N66001-84-R0030. Within this document, the ANSI X3.64 Compatible Virtual Terminal is referred to as the Virtual Terminal. 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.3 SCOPE This document describes the procedures for testing the Virtual Terminal after it is developed. The test procedures defined in this document will show compliance with the requirements of the Proposal to Design and Implement an ANSI X3.64 Compatible Virtual Terminal in Ada [TI84]. 1.4 SUMMARY The objective of this document is to explain the test procedures that are necessary for acceptance testing of the Virtual Terminal. Acceptance testing will demonstrate that the requirements of the Proposal to Design and Implement a Virtual Terminal in Ada [TI84] 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 2.1 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. [TI84 ] Texas Instruments, "Proposal to Design and Implement an ANSI X3.64 Compatible Virtual Terminal in Ada", Lewisville, Tx, January 1984. [NAV78B] Navy, "Data Item Description, Computer Program Test Specifications", Navy DI-E-2143, 29 November 1978. 2-1 CHAPTER 3 3.1 TESTING REQUIREMENTS 3.2 GENERAL Acceptance testing of the Virtual Terminal must verify the requirements in the proposal [TI84] for the Virtual Terminal. 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 Virtual Terminal satisfies its original objectives. Appendix A contains the test specifications for the Virtual Terminal. 2. Create Test Data - The second step is to create test data to satisfy the test specifications. The data is a series of Ada source programs which will fully test the requirements stated in the proposal. These programs will be used as input to the Virtual Terminal. 3. Analyze Results - The third step is to conduct testing and analyze the results. The Virtual Terminal is executed with the test data that was created in step 2. The results are analyzed and the appropriate matrices are updated. Located in Appendix B are two matrices developed to assist the reader of this document. The first matrix indicates each Test Specification and the requirements it deals with. The second matrix denotes each of the requirements listed in the proposal and the location ,within this document, of the Test Procedure which satisfies the particular requirement. 3-1 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. 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.3 VIRTUAL TERMINAL ACCEPTANCE/PREOPERATING PROCEDURES The following paragraphs explain the necessary preparations and procedures for acceptance testing of the Virtual Terminal. 3.3.1 EQUIPMENT PREPARATION In order to complete acceptance testing, the Virtual Terminal must be available on a Data General MV 10,000 running under AOS/VS. 3.3.2 DIGITAL PROCESSOR PREPARATION In order to complete acceptance testing, the ROLM/Data General Ada Development Environment (ADE) must be available. 3-2 3.3.3 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. The remainder of this section contains the Test Procedures which ,when implemented, will fully test the Virtual Terminal. Each procedure references the Test Specification Matrix located in Appendix A where more information is located. As noted in step 2, input files for the Virtual Terminal (Ada source programs) must be created to satisfy all of the test specifications in Appendix A. Then, when the Virtual Terminal is ready to undergo acceptance testing, step 3 is started. Thus, the input files are executed. The expected output is somewhat difficult to analyze since it deals entirely with a display and not specific output files. NOTE One Ada source program may be used to satisfy a number of test specifications in Appendix A. In other words, it is not necessary to create a separate input file for each test specification in Appendix A. 3-3 3.3.3.1 TESTING SETTING TAB STOPS 3.3.3.1.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which tests the set_tab and moving by tabs requirements. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to signal where the cursor was located at a certain point in the test. set_position( 5 ) ; set_tab ; set_position( 15 ) ; set_tab ; new_line ; tab ; put('C') ; --'C' should be in col 5 update_line ; tab ; put('C') ; --'C' should be in col 15 update_line ; 3.3.3.1.2 Description Of The Actual Display After the first update_line, a 'C' should be located in the 5th column of the display, after the second update line a 'C' should be located in column 15. Therefore the set_tab procedure correctly places tab stops where the act. pos. is located, and the procedure tab moves to these positions as indicated. Matrix entry number: A-1 3-4 3.3.3.2 TESTING CLEARING TAB STOPS 3.3.3.2.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which tests the clear_tab and moving by tabs requirements. ____ **Note: Where appropriate, an uppercase 'C' will be inserted into the display to indicate where the cursor was located at a certain point in the test. set_position( 5 ) ; set_tab ; put('C') ; --tab stop will be located at the 'C' new_line ; --new_line has an implicit call on update_line tab ; update_line ; --cursor will be in column 5 clear_tab ; --clears tab in column 5 new_line ; --positions cursor at beginning of next line tab ; put('C') ; --'C' will be in 1st col of next line 3.3.3.2.2 Description Of The Actual Display After the first new_line, a 'C' will be located at the tab stop in the 5th column of the first line, when the final call on tab is performed the cursor will be left at the beginning of the next line since no tab stops are present on the line. There will be 1 blank line between 'C's. Matrix entry number: A-2 3-5 3.3.3.3 TESTING MOVING BY TAB STOPS 3.3.3.3.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which tests the moving by tabs and the setting tab stops requirements. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. put( "Here I am." ) ; --to help keep track of your orig. position new_line( 2 ) ; --puts act. pos. at beginning of next line tab ; put('C') ; --cursor should be at the beginning of next line set_position( 10 ) ; --act. pos. in col 10 set_tab ; new_line ; tab ; put('C') ; --'C' will be in col 10 update_line ; set_position( 15 ) ; --position act. pos. past tab stop tab ; update_line ; --no operation will occur new_line ; tab( 3 ) ; put('C') ; update_line ; --only one tab stop has been set so that's all that --will be invoked 3.3.3.3.2 Description Of The Actual Display There will be 1 blank line between 'Here I am.' and the first 'C'. The following line will contain a 'C' in column 10. The next line will contain a 'C' in column 10, on the next line. Matrix entry number: A-3 3-6 3.3.3.4 TESTING MOVING TO A NEW LINE 3.3.3.4.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which tests the moving to a new line and moving to a tab stop requirements. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to signal where the cursor was located at a certain point in the test. put( "Here I am." ) ; --to help keep track of the number of new lines set_position( 15 ) ; new_line ; --cursor will be at the beginning of next line put( 'C' ) ; set_position( 10 ) ; set_tab ; new_line ; tab ; put('C') ; --cursor will be in col 10 new_line( 3 ) ; put('C') ; --cursor will be in col 1 update_line ; 3.3.3.4.2 Description Of The Actual Display The first 'C' will be located in column 1 of the line below 'Here I am.'. The second 'C' will be found in column 10 of the line below the first 'C'. Newline is then called with a parameter of 3, the last 'C' will be located in column 1, 3 lines below the last 'C'(two blank lines will separate the 'C's. The cursor will be located just past the last 'C'. Matrix entry number: A-4 3-7 3.3.3.5 TESTING MOVING TO A NEW PAGE 3.3.3.5.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the moving to a new page requirement( if your terminal supports this function). ____ **Note: An uppercase 'C' will be inserted, where appropriate, in the display to signal where the cursor was located at a certain point in the test. put( "Here I am." ) ; --to help keep track of your original position set_position( 15 ) ; new_page ; --call new page from the middle of a line --notice the default is 1 for new page put( 'C' ) ; --cursor will be at the beginning of next page new_page( 2 ) ; --2 new pages will be performed put( 'C' ) ; update_line ; 3.3.3.5.2 Description Of The Actual Display The 'C' will be located at the beginning of a new page. 'Here I am.' will be shown on the actual display since newpage does an implicit call on updateline. The second 'C' will be located at the beginning of the another page. New_page is defined as an ascii form feed and cannot be changed. Matrix entry number: A-5 3-8 3.3.3.6 TESTING WRITING CHARACTERS AND STRINGS TO THE DISPLAY 3.3.3.6.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the writing chars and strings to the display requirement. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. put('x') ; --act. pos. will be just past 'x' update_line ; set_position( 10 ) ; put( "Here I am." ) ; set_position( 60 ) ; put( "The end of this string will be lost." ) ; 3.3.3.6.2 Description Of The Actual Display The 'x' will be in column 1, the next string will start in column 10. The last string will be written to the display but when the column number reaches it's maximum, the remaining chars will be lost. Matrix entry number: A-6 3-9 3.3.3.7 TESTING READING CHARACTERS AND STRINGS FROM THE KEYBOARD 3.3.3.7.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the reading chars and strings from the keyboard requirement. This requirement is implementation dependent. The number of key strokes returned from a call on get may vary from a single key to many keys depending on the machine the VT is hosted on. Because of these implementation restraints, outer loops may be needed( as shown ) to extract all the key strokes from the keyboard. Write_to_screen will be a procedure used to display the contents of variables on the screen so the person performing these tests will be able to see the results immediately. The user will have to type a '#' key to exit from each test loop. NOTE There are several procedures used here which are not defined. They will be developed when the test procedures are conducted. procedure do_get ; loop get(data, last, keys, timeout) ; num_of_function_keys := function_count( keys ) ; if last = 0 then if num_of_function_keys = 0 then null ; else for index in 1 .. num_of_function_keys loop function_key( keys, index, id, position ) ; handle_the_function_key( id ) ; end loop ; end if ; else if num_of_function_keys = 0 then handle_the_string( data, last ) ; else last_position := 1 ; for index in 1 .. num_of_function_keys loop function_key( keys, i, id, position ) ; if position <> 0 then handle_the_string( data(last_position .. position ), 3-10 (position - last_position + 1) ) ; last_position := position + 1 ; end if ; handle_the_function_key( id ) ; end loop ; end if ; if last /= 0 then exit when data(last) = '#' ; end if ; end loop ; --****************************************************** get( data, last, keys ) ; --clear out any garbage --*** You must type in a '#' after each series of input chars *** do_get ; --type in just chars do_get ; --type in just function keys do_get ; --type in chars first then function keys do_get ; --type in function keys first then chars do_get ; --type in chars and function keys intermixed 3.3.3.7.2 Description Of The Actual Display The actual display will not be affected by these tests. The get procedure only deals with information coming from the keyboard and does not change the virtual or actual display. But to display the incoming characters and function keys they will be output to the screen in some manner to be decided later. Matrix entry number: A-7 3-11 3.3.3.8 TESTING RINGING THE TERMINAL'S BELL 3.3.3.8.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the ringing the terminal's bell requirement. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. bell ; put('Ring the bell.') ; bell ; update_line ; 3.3.3.8.2 Description Of The Actual Display The bell, as it is described in the TCF, will be rung twice, with a line of data in between. Matrix entry number: A-8 3-12 3.3.3.9 TESTING SETTING TAB STOPS 3.3.3.9.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which tests the set_tab and moving by tabs requirements. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to siganl where the cursor was located at a certain point in the test. set_position( 5, 15 ) ; set_tab ; set_position( 15, 25 ) ; set_tab ; set_position( 10, 1 ) ; --act. pos. will be in col 1 of line 16 tab ; put('C') ; --'C' should be in col 15 tab ; put('C') ; --'C' should be in col 25 update_screen_with_movement ; 3.3.3.9.2 Description Of The Actual Display After the update screen, a 'C' should be located in the 15th column of the display and a 'C' should be located in column 25 of the 16th line. Therefore the set_tab procedure correctly places tab stops where the act. pos. is located, and the procedure tab moves to these positions as indicated. Matrix entry number: A-9 3-13 3.3.3.10 TESTING CLEARING TAB STOPS 3.3.3.10.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which tests the clear_tab and moving by tabs requirements. ____ **Note: Where appropriate, an uppercase 'C' will be inserted into the display to indicate where the cursor was located at a certain point in the test. set_position( 5, 15 ) ; set_tab ; set_position( 5, 25 ) ; set_tab ; set_position( 10, 1 ) ; tab ; put('C') ; tab ; put('C') ; set_position( 17, 1 ) ; tab ; clear_tab ; --clears tab in column 15 insert_line ; --positions cursor at beginning of new line tab ; --no operation will occur put('C') ; update_screen_with_movement ; 3.3.3.10.2 Description Of The Actual Display After the first update_line, a 'C' will be located at the tab stop in the 15th and 25th column of the tenth line, when the final call on tab is performed the cursor will be at the 25th column since the first tab stop has been erased. Matrix entry number: A-10 3-14 3.3.3.11 TESTING MOVING TO A TAB STOP 3.3.3.11.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which tests the moving by tabs and the setting tab stops requirements. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. put( "Here I am." ) ; --to help keep track of your orig. position insert_line ; --puts act. pos. at beginning of new line tab ; --no operation will occur set_position( 2, 5 ) ; --act. pos. in col 5 set_tab ; set_position( 2, 25) ; set_tab ; set_position( 18, 1 ) ; tab( 2 ) ; put('C') ; --'C' will be in col 25 of line 18 update_line ; set_position( 19, 1 ) ; tab ; put('C') ; update_screen_with_movement ; 3.3.3.11.2 Description Of The Actual Display No operation will occur after the first call on tab since there where no tab stops set. Then a call on tab(2) will position the cursor at col. 25 (two tabs stops from col 1). The final call on tab will move the cursor to column 5. Matrix entry number: A-11 3-15 3.3.3.12 TESTING MOVING TO A NEW LINE 3.3.3.12.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which tests the moving to a new line and moving to a tab stop requirements. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to signal where the cursor was located at a certain point in the test. put( "Here I am." ) ; --to help keep track of the number of new lines set_position( 1, 1 ) ; insert_line ; --cursor will be at the beginning of next line set_position(1,1) ; insert_line( 3 ) ; set_position(24, 1) ; put("This the bottom line") ; update_screen_with_movement ; set_position( 12, 60 ) -- any position will fo insert_line ; update_screen_with_movement ; 3.3.3.12.2 Description Of The Actual Display First a line is written on the top of the display. A single line is inserted above it , then 3 lines are inserted above it. The screen scrolls down as lines are inserted. A line is then printed on the bottom row. A call on insertline pushes the bottom row off the display, it is lost. Matrix entry number: A-12 3-16 3.3.3.13 TESTING MOVING TO A NEW PAGE 3.3.3.13.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the moving to a new page requirement. ____ **Note: An uppercase 'C' will be inserted, where appropriate, in the display to signal where the cursor was located at a certain point in the test. put( "Here I am." ) ; --to help keep track of your original position set_position( 15, 5 ) ; erase_in_display( all_positions ) ; --these two statements set_position( 1, 1 ) ; --perform the new page set_position( 24, 1 ) ; put("This is a new page.") ; update_screen_with_movement ; 3.3.3.13.2 Description Of The Actual Display The line output will be located at the bottom of the new page. ***note -- page terminal does not have a new_page procedure but it can be easily accomplished using the above technique. Matrix entry number: A-13 3-17 3.3.3.14 TESTING WRITING CHARACTERS AND STRINGS TO THE DISPLAY 3.3.3.14.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the writing chars and strings to the display requirement. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. set_position( 5, 1 ) ; put('x') ; --act. pos. will be just past 'x' update_line ; set_position( 1, 1 ) ; put( "Here I am." ) ; set_position( 15, 60 ) ; put( "The end of this string will be lost." ) ; update_screen_with_movement ; 3.3.3.14.2 Description Of The Actual Display The 'x' will be in column 1 of line 5, the first string will start in column 1 of line 1. The last string will be written to the display but when the column number reaches it's maximum, the remaining chars will be lost. This might be dependent upon the terminal which the user is working on so the final test of this procedure might not be performed. Matrix entry number: A-14 3-18 3.3.3.15 TESTING READING CHARACTERS AND STRINGS FROM THE KEYBOARD 3.3.3.15.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the reading chars and strings from the keyboard requirement. This requirement is implementation dependent. The number of key strokes returned from a call on get may vary from a single key to many keys depending on the machine the VT is hosted on. Because of these implementation restraints, outer loops may be needed( as shown ) to extract all the key strokes from the keyboard. Write_to_screen will be a procedure used to display the contents of variables on the screen so the person performing these tests will be able to see the results immediately. The user will have to type a '#' key to exit from each test loop. NOTE There are several procedures used here which are not defined. They will be developed when the test procedures are developed. procedure do_get ; loop get(data, last, keys, timeout) ; num_of_function_keys := function_count( keys ) ; if last = 0 then if num_of_function_keys = 0 then null ; else for index in 1 .. num_of_function_keys loop function_key( keys, index, id, position ) ; handle_the_function_key( id ) ; end loop ; end if ; else if num_of_function_keys = 0 then handle_the_string( data, last ) ; else last_position := 1 ; for index in 1 .. num_of_function_keys loop function_key( keys, i, id, position ) ; if position <> 0 then handle_the_string( data(last_position .. position ), 3-19 (position - last_position + 1) ) ; last_position := position + 1 ; end if ; handle_the_function_key( id ) ; end loop ; end if ; if last /= 0 then exit when data(last) ='#' end if ; end loop ; --****************************************************** get( data, last, keys ) ; --clear out any garbage --*** You must type in a '#' after each series of input chars *** do_get ; --type in just chars do_get ; --type in just function keys do_get ; --type in chars first then function keys do_get ; --type in function keys first then chars do_get ; --type in chars and function keys intermixed 3.3.3.15.2 Description Of The Actual Display The actual display will not be affected by the 'get'. The 'get' procedure only deals with information coming from the keyboard and does not change the virtual or actual display, but to hsow the user that the 'get' procedure is working properly, the incoming keys will be displayed by this test procedure in a manner which will be decided later. Matrix entry number: A-15 3-20 3.3.3.16 TESTING RINGING THE TERMINAL'S BELL 3.3.3.16.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the ringing the terminal's bell requirement. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. put("Ring the bell.") ; bell; bell ; bell ; update_line ; 3.3.3.16.2 Description Of The Actual Display The bell, as it is described in the TCF, will be rung three times. Matrix entry number: A-23 3-21 3.3.3.17 TESTING DELETING CHARACTERS FROM THE DISPLAY 3.3.3.17.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the deleting characters from the display requirement for the page_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. set_position( 8, 1 ) ; put("this is our fourth line of data") ; update_screen_with_movement ; set_position( 8, 13 ) ; delete_character( 6 ) ; --'fourth' should be deleted update_screen_with_movement ; set_position( 22, 1) ; put("this is our first line of data") ; set_position( 22,12 ) ; delete_character(25) ; update_screen_with_movement ; 3.3.3.17.2 Description Of The Actual Display Fourth will be deleted from the display. When something is deleted within a line the chars remaining on the line shift to the left to fill in for the deleted chars. The second line will be deleted from the middle to the end of line, blanks fill from the right as characters are deleted. Matrix entry number: A-16 3-22 3.3.3.18 TESTING DELETING LINES FROM THE DISPLAY 3.3.3.18.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the deleting lines from the display requirement for the page_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. set_position( 1, 1 ) ; --the following calls on put("This is the top line") ; --put are used to set set_position( 8, 1 ) ; --up the display, so put("delete lines from display") ; --we can more easily set_position( 9, 1 ) ; --see delete_line in put("line number one") ; --action set_position( 10, 1 ) ; put("line number two") ; set_position( 11, 1 ) ; put("line number three") ; set_position( 12, 1 ) ; put("This line should not be deleted") ; update_screen_with_movement ; set_position( 10, 1 ) ; --the 2nd and 3rd lines will be deleted delete_line(2) ; --the lines below will shift up update_screen_with_movement ; set_position( 23, 1 ) ; --delete from the middle of a line put("This is our fourth line of data") ; set_position( 24, 1 ) ; put("this is our last line of data") ; set_position( 23, 10 ) ; --delete more than number of delete_line( 5 ) ; --lines left on the display update_screen_with_movement ; 3.3.3.18.2 Description Of The Actual Display There will only be one line left on the screen. When lines are deleted, the lines remaining below the active position shift up and blank lines fill from the bottom. Matrix entry number: A-17 3-23 3.3.3.19 TESTING ERASING CHARACTERS FROM THE DISPLAY 3.3.3.19.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the erasing characters from the display requirement for the page_mode terminal. ____ **Note: The testing of this requirement may not look like the following Ada source code might indicate. Erase_in_display will be used while testing many of the other requirements where it will get tested sufficiently. Therefore the following is just an example of how it could be tested. set_position( 1, 1 ) ; --the following calls on put("This is the top line") ; --put are used to set set_position( 5, 1 ) ; --up the display, so put("erasing chars from display") ; --we can more easily set_position( 6, 1 ) ; --see erase_in_display in put("line number one") ; --action set_position( 7, 1 ) ; put("line number two") ; set_position( 8, 1 ) ; put("line number three") ; set_position( 10, 1 ) ; put("This line should not be deleted") ; set_position( 24, 1 ) ; put("This is the bottom line of the display") ; update_screen_with_movement ; set_position( 1, 1 ) ; --nothing will happen erase_in_display( from_start_to_xy_position ) ; update_screen_with_movement ; set_position( 24, 80 ) ; --nothing will happen erase_in_display( from_xy_position_to_end ) ; update_screen_with_movement ; set_position( 5, 10 ) ; --display will be erased from start erase_in_display( from_start_to_xy_position ) ; --to act. pos. update_screen_with_movement ; set_position( 10, 10 ) ; --erase from act. pos. to end erase_in_display( from_xy_positon_to_end ) ; update_screen_with_movement ; set_position( 7, 60 ) ; erase_in_display( all_positions ) ; update_screen_with_movement ; 3-24 3.3.3.19.2 Description Of The Actual Display The entire screen will be erased by the final erase_in_display. The other calls on erase_in_display are self explanatory. Nothing happens when the procedure is called to erase to the act. pos. when the act. pos. is at the first position of the display( likewise for erasing to the end of the display while you are at the end of the display ). The act. pos. does not move after an erase. Matrix entry number: A-18 3-25 3.3.3.20 TESTING ERASING BETWEEN SPECIFIC POSITIONS ON THE DISPLAY 3.3.3.20.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the erasing between specific positions on the display requirement for the page_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. set_position( 1, 1 ) ; --the following calls on put("This is the top line") ; --put are used to set set_position( 8, 1 ) ; --up the display, so put("erasing chars from display") ; --we can more easily set_position( 9, 1 ) ; --see erase_in_line in put("line number one") ; --action set_position( 10, 1 ) ; put("line number two") ; set_position( 11, 1 ) ; put("line number three") ; update_screen_with_movement ; set_position( 1, 1 ) ; --nothing will happen erase_in_line( from_start_to_xy_position ) ; update_screen_with_movement ; set_position( 24, 80 ) ; --nothing will happen erase_in_line( from_xy_position_to_end ) ; update_screen_with_movement ; set_position( 8, 10 ) ; --line will be erased from start erase_in_line( from_start_to_xy_position ) ; --to act. pos. update_line ; set_position( 7, 5 ) ; --erase from act. pos. to end erase_in_line( from_xy_positon_to_end ) ; update_line ; set_position( 8, 60 ) ; erase_in_line( all_positions ) ; update_line ; 3-26 3.3.3.20.2 Description Of The Actual Display The act. pos. is not moved after an erase of any kind. The scope of this erase procedure is just one line. The parameter 'from_start_to_xy_position' means from the start of the line to the active position. Matrix entry number: A-19 3-27 3.3.3.21 TESTING INSERTING CHARACTERS ONTO THE DISPLAY 3.3.3.21.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the inserting characters onto the display requirement for the page_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. set_position( 1, 1 ) ; --the following calls on put("This is the top line") ; --put are used to set set_position( 5, 1 ) ; --up the display, so put("insert characters onto display") ; --we can more easily set_position( 6, 1 ) ; --see erase_in_line in put("line number one") ; --action set_position( 7, 1 ) ; put("line number two") ; set_position( 8, 1 ) ; put("line number three") ; set_position( 24, 1 ) ; put("This is the bottom line of the display") ; update_screen_with_movement ; set_position( 8, 1 ) ; enter_insert_mode ; put("This is a test ") ; update_screen_with_movement ; set_position( 12, 40 ) ; exit_insert_mode ; put("the end of this line will be lost") ; enter_insert_mode ; set_position( 12, 40 ) ; put("if the max col is exceeded, ") ; update_screen_with_movement ; set_position( 7, 5 ) ; exit_insert_mode ; write_to_screen("Out of insert mode") ; --This will write over update_line ; -- whatever is there 3-28 3.3.3.21.2 Description Of The Actual Display There will be two lines changed from the original state. Once insert mode is exited, chars will not be inserted on the display, they will be written over whatever was previously in that position. Matrix entry number: A-20 3-29 3.3.3.22 TESTING INSERTING LINES ONTO THE DISPLAY 3.3.3.22.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the inserting lines into the display requirement for the page_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. set_position( 1, 1 ) ; --the following calls on put("This is the top line") ; --put are used to set set_position( 5, 1 ) ; --up the display, so put("insert lines into display") ; --we can more easily set_position( 6, 1 ) ; --see insert_line in put("line number one") ; --action set_position( 7, 1 ) ; put("line number two") ; set_position( 8, 1 ) ; put("line number three") ; set_position( 24, 1 ) ; put("This is the bottom line of the display") ; update_screen_with_movement ; set_position( 1, 1 ) ; insert_line ; update_screen_with_movement ; set_position( 24, 1 ) ; put("This is the new bottom line") ; set_position( 24, 1 ) ; insert_line ; update_screen_with_movement ; --bottom line of data is lost set_position( 7, 1 ) ; insert_line( 3 ) ; update_screen_with_movement ; 3.3.3.22.2 Description Of The Actual Display There will be several lines inserted into the display. These lines will be blank and the cursor will be at the beginning of the newly inserted line. Lines below the act. pos. are pushed downward in the display. The final image of the display will have the cursor located first position of the seventh line. Matrix entry number: A-21 3-30 3.3.3.23 TESTING SETTING THE GRAPHIC RENDITION ON THE DISPLAY 3.3.3.23.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the setting the graphic rendition on the display requirement for the page_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. set_position( 1, 1 ) ; --the following calls on put("This is the top line") ; --put are used to set set_position( 5, 1 ) ; --up the display, so put("setting rendition of display") ; --we can more easily set_position( 6, 1 ) ; --see select_graphic_ put("line number one") ; --rendition set_position( 7, 1 ) ; put("line number two") ; set_position( 8, 1 ) ; put("line number three") ; set_position( 24, 1 ) ; put("This is the bottom line of the display") ; update_screen_with_movement ; set_position( 1, 22 ) ; select_graphic_rendition( reverse_image ) ; put("This should be highlited.") ; update_screen_with_movement ; set_position( 3, 22 ) ; select_graphic_rendition( reverse_image ) ; put("Rendition should not change") ; update_screen_with_movement ; set_position( 15, 22 ) ; select_graphic_rendition( primary_rendition ) ; put("Back to normal") ; update_screen_with_movement ; 3.3.3.23.2 Description Of The Actual Display There should be two lines written in reverse image on the display which is normally dark letters on a lite background. The last line of data written to the display will be in the normal rendition. Matrix entry number: A-22 3-31 3.3.3.24 TESTING DEFINING QUALIFIED AREAS ON THE DISPLAY 3.3.3.24.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the defining qualified areas on the display requirement for the form_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. set_position( 5, 1 ) ; define_qualified_area( high, unprotected, numerics); set_position( 6, 10 ) ; define_qualified_area( normal, protected, graphic_characters) ; set_position( 20, 20 ) ; define_qualified_area( none, unprotected, graphic_characters) ; activate_form ; --will be at first unprotected area, --control is passed to the keyboard 3.3.3.24.2 What The Tester Has To Type When activate form is invoked, control shifts to the keyboard and the tester. The act. pos. will be at the first editing position of the form. Type in some numbers, they should appear in high intensity. Try typing some letters, they will not be allowed. Try typing some chars in a protected area, the bell should ring( as defined in the TCF ). Hit the tab. Type in any grpahic characters. They will not appear on the display because the intensity is set to none. 3.3.3.24.3 Description Of The Actual Display There will be three qualified areas defined on the form. Each with various characteristics as defined in the calls on define_qualified_area. Matrix entry number: A-24 3-32 3.3.3.25 TESTING CLEARING QUALIFIED AREAS ON THE DISPLAY 3.3.3.25.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the clearing qualified area from the display requirement for the form_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted in the display to indicate where the cursor was located at a certain point in the test. set_position( 5, 1 ) ; define_qualified_area( high, unprotected, numerics ) ; set_position( 6, 10 ) ; define_qualified_area( normal, protected, graphic_characters) ; set_position( 20, 20 ) ; define_qualified_area( none, unprotected, graphic_characters ) ; tab ; tab ; --will position the act. pos. --at the second qualified area --of the form clear_qualified_area ; --at position (6,10) activate_form ; --will be at first unprotected area --form editing is now allowed set_position( 20,30 ) ; clear_qualified_area ; activate_form ; 3.3.3.25.2 What The Tester Needs To Type When the form is activated, control is passed from the user program to the keyboard. The tester must now use the local editing allowed to illustrate the properties of the form at hand. The tab key must be hit to show that the second qualified area is no longer defined. The tester then needs to hit a function key to return control to the user program, where another area is cleared. Activate the form again. The cursor will now be at the first editing position on the form which will be the first qualified area initially defined. 3-33 3.3.3.25.3 Description Of The Actual Display There will be two qualified areas defined on the form when it is first activated. Both with various characteristics as defined in the calls on definequalifiedarea. Then the third one is cleared. The screen will consist of a single qualified area in high rendition. Matrix entry number: A-25 3-34 3.3.3.26 TESTING MOVING BY TAB STOPS ON THE DISPLAY 3.3.3.26.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the moving by tab stops on the display requirement for the form_mode terminal. Moving by tab stops to the next qualified area can take two forms in the form_mode terminal. One can be done within the user program with the procedure tab and the other can be performed by hitting the tab key while the form is active. ____ **Note: Where appropriate, an uppercase 'C' will be inserted into the display to indicate where the cursor was located at a certain point in the test. set_position( 5, 1 ) ; define_qualified_area( high, unprotected, numerics) ; set_position( 6, 10 ) ; define_qualified_area( normal, protected, graphic_characters ) ; set_position( 20, 20 ) ; define_qualified_area( none, unprotected, graphic_characters ) ; tab ; tab ; --will position the act. pos. --at the second qualified area --of the form, this will not be --because the area is protected put("NAME:") ; tab ; --at the third qual. area defined put("PASSWORD:") ; activate_form ; --will be at first unprotected area 3.3.3.26.2 What The Tester Needs To Type When the form is activated, control is passed from the user program to the keyboard. The tester must now use the local editing allowed to illustrate the properties of the form at hand. Hit the tab key to show that the cursor moves to the next unprotected qualified area. Tab to the last unprotected qualified area on the form, hit the tab key again, the cursor will move to the first qualified area of the form. 3-35 3.3.3.26.3 Description Of The Actual Display There will be three qualified areas defined on the form. The form_mode terminal has line wrap and screen wrap capabilities. 'NAME:' and 'PASSWORD:' will appear on the screen. Matrix entry number: A-26 3-36 3.3.3.27 TESTING ERASING BETWEEN SPECIFIED POSITIONS ON THE DISPLAY 3.3.3.27.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the erasing between specified areas on the display requirement for the form_mode terminal. Erasing from the display can occur within specified areas or the entire display may be erased. ____ **Note: Where appropriate, an uppercase 'C' will be inserted into the display to indicate where the cursor was located at a certain point in the test. set_position( 5, 1 ) ; define_qualified_area( high, unprotected, numerics ) ; set_position( 6, 10 ) ; define_qualified_area( normal, protected, graphic_characters ) ; set_position( 20, 20 ) ; define_qualified_area( none, unprotected, graphic_characters ) ; tab ; --will position the act. pos. --at the first qualified area put("Here I am.") ; redisplay_screen_with_movement ; tab ; --back at first qualified area put("This should not appear on the screen.") ; set_position( 6, 40 ) ; erase_area ; activate_form ; erase_display ; activate_form ; 3.3.3.27.2 What The Tester Needs To Type The tester needs to type the chars allowed in the first and third qualified areas. Then a function key to return control to the users program where the display is to be erased. The tester will notice that the entire display is erased. Try typing some chars from the keyboard. The bell will ring( as defined in the TCF ) because the whole screen is protected. Hit a function key to return to the users program. 3-37 3.3.3.27.3 Description Of The Actual Display The first form illustrates the erase area command. After writing a string in the second qualified area, the active position is placed within that area and erase_area is called. This blanks out the area where the act. pos. is located. In the second form, there will be one qualified area defined. The entire display will be blank, the erase_display blanks out the whole virtual display. All user defined qualified areas are removed from the display. Matrix entry number: A-28 and A-29 3-38 3.3.3.28 TESTING READING CHARACTERS AND STRINGS FROM THE DISPLAY BUFFER 3.3.3.28.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the reading chars and strings from the display requirement for the form_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted into the display to indicate where the cursor was located at a certain point in the test. set_position( 5, 1 ) ; define_qualified_area( high, unprotected, numerics ) ; set_position( 6, 10 ) ; define_qualified_area( normal, protected, graphic_characters ) ; set_position( 20, 20 ) ; define_qualified_area( none, unprotected, graphic_characters ) ; activate_form ; tab ; --move to the first area defined get( item ) ; set_position( 22, 10 ) ; --will produce same string typed put( item ) ; --at the first qualified area tab ; tab ; get( item2 ) ; set_position( 23, 10 ) ; put( item2 ) ; activate_form ; 3.3.3.28.2 What The Tester Needs To Type The tester needs to type the chars allowed in the first and third qualified areas. Then a function key to return control to the users program where the strings entered in the qualified areas can be read. The function 'get' will extract the number of characters from the display equal to the size of the array as it was declared( ex. item1(1..5) will result in 5 characters being extracted from the form with get( item1 ) ). 3-39 3.3.3.28.3 Description Of The Actual Display There will be three qualified areas defined on the form, two of them will recieve data from the keyboard. The data should be read and output to the screen to assure the get procedure works properly. Matrix entry number: A-27 3-40 3.3.3.29 TESTING WRITING CHARACTERS AND STRINGS TO THE DISPLAY BUFFER 3.3.3.29.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the writing of chars and strings to the display requirement for the form_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted into the display to indicate where the cursor was located at a certain point in the test. set_position( 5, 1 ) ; define_qualified_area( high, unprotected, graphic_characters ) ; set_position( 6, 1 ) ; define_qualified_area( none, unprotected, graphic_characters ) ; set_position( 20, 20 ) ; define_qualified_area( normal, unprotected, numerics ) ; tab ; put("This is the first string") ; set_position( 20, 60 ) ; put("This is the second string, it should wrap to the next line") ; set_position( 24, 60 ) ; put("This is the third string, it should wrap screen") ; activate_form ; 3.3.3.29.2 What The Tester Needs To Type The tester need only type a function key to return to the user's program. 3.3.3.29.3 Description Of The Actual Display The display will have three strings in it. They will sufficiently describe the capabilities of the put procedure. Matrix entry number: A-31 3-41 3.3.3.30 TESTING ACTIVATING A FORM FOR USER FILL IN 3.3.3.30.1 Contents Of The Test The following test procedure consists of a segment of Ada procedure calls which test the activating a form for user fill in requirement for the form_mode terminal. ____ **Note: Where appropriate, an uppercase 'C' will be inserted into the display to indicate where the cursor was located at a certain point in the test. set_position( 5, 1 ) ; put("NAME:") ; set_position( 5, 10) ; define_qualified_area( high, unprotected, graphic_characters ) ; set_position( 6, 1 ) ; put("PASSWORD:") ; set_position( 6, 10 ) ; define_qualified_area( none, unprotected, graphic_characters ) ; set_position( 20, 20 ) ; define_qualified_area( normal, unprotected, numerics ) ; activate_form ; --perform local editting while --this form is active, this includes: --tabing to the next unprotected qualified --area, using arrow keys, deleting chars --from the display, using carriage --return to get to the next line, and --hitting a function key to return to --the user program --write to a protected area, the bell --will ring 3.3.3.30.2 What The Tester Needs To Type All the local editting must be tested while the form is active. The types of editting are described to the right of the call on activate form above. The tester must type a function key to return control to the user's program. 3-42 3.3.3.30.3 Description Of The Actual Display The actual display will vary as to the types and quantity of the local editting down by the tester. Matrix entry number: A-30 3-43 CHAPTER 4 4.1 TEST MANAGEMENT The Virtual Terminal development team is responsible for management of the testing described in this document. The Virtual Terminal development team responsibilities are to: o create test data according to the test specifications in Appendix A 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 5.1 PERSONNEL REQUIREMENTS The software development team for the Virtual Terminal is the only personnel required to complete the acceptance testing described in this document. 5-1 CHAPTER 6 6.1 HARDWARE REQUIREMENTS The acceptance testing described in this document shall be conducted on a Data General MV 10,000 running under AOS/VS. 6-1 CHAPTER 7 7.1 SOFTWARE REQUIREMENTS The acceptance testing described in this document requires the ROLM/Data General Ada Development Environment (ADE). 7-1 CHAPTER 8 8.1 TESTING SCHEDULE The acceptance testing described in this document will take 1-2 months to complete. 8-1 CHAPTER 9 9.1 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 Virtual Terminal. Each test specification includes a list of the requirements that are satsified, 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. The remainder of this appendix is divided into three large groups. Each group contains the Test Specifications for one of the 'modes' of the Virtual Terminal. The specifications are grouped in the following order: Scroll_mode, Page_mode, and Form_mode. A-1 TEST SPECIFICATIONS TEST SPECIFICATIONS FOR THE SCROLL MODE TERMINAL A.1 SET_TAB A.1.1 REQUIREMENTS MET BY TEST This test specification satisfies the tab stop setting requirement for the scroll_mode terminal. A.1.2 DESCRIPTION OF TEST The test shall include making a call on set_tab followed by a call on update_line. The call on set_tab should position a tab stop at the current active position on the virtual display. The tab stop should remain in the same column on succeeding lines. We will then make a call on tab after a new_line has been issued to see if the set_tab worked properly. A.1.3 ASSUMPTIONS The scroll_mode terminal must be opened prior to the test. 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 call on set_tab tab stop set at facility active position 2 call on set_tab tab stop remains facility while active position no apparent is on a tab stop action A-2 TEST SPECIFICATIONS A.2 CLEAR_TAB A.2.1 REQUIREMENTS MET BY TEST This test specification satisfies the clear tab stop requirement for the scroll_mode terminal. A.2.2 DESCRIPTION OF TEST The test shall include removing a tab stop at the active position on the scroll mode terminal. A.2.3 ASSUMPTIONS The scroll_mode terminal must be opened prior to the test. A.2.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 call on clear_tab tab stop removed facility while active position is on a tab stop 2 call on clear_tab no apparent facility while active position action is not on a tab stop A-3 TEST SPECIFICATIONS A.3 TAB A.3.1 REQUIREMENTS MET BY TEST This test specification satisfies the moving to a tab stop requirement for the scroll_mode terminal. A.3.2 DESCRIPTION OF TEST The test shall include moving the active position to a tab stop from the current active position on the scroll mode terminal. A.3.3 ASSUMPTIONS The scroll_mode terminal must be opened prior to the test. A.3.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 call on tab with no move to the begin- facility tab stops set, ning of the next update line line 2 call on tab with a the act. pos. should facility tab stop remaining be moved to this tab to the right of the stop active position 3 call on tab while the the act. pos should facility act. pos. is to the be positioned at the right of a tab stop, first tab stop on the update line next line 4 call on tab with a the active postion facility the parameter count will be moved the equal to some number specified number of tab greater than one, stops update line A-4 TEST SPECIFICATIONS A.4 NEW_LINE A.4.1 REQUIREMENTS MET BY TEST This test specification satisfies the moving to a new line requirement for the scroll_mode terminal, and the setting tab stops requirement. A.4.2 DESCRIPTION OF TEST The test shall include moving the active position to a new line from the current active position on the scroll mode terminal. A.4.3 ASSUMPTIONS The scroll_mode terminal must be opened prior to the test. A.4.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 call new_line from the active position facility the beginning, end, should move to the and some internal beginning of the position on the line next line 2 call new_line with the tab stop should facility a tab stop set on the remain on the the line next line, new_ line postions the act. pos. at the beginning of the next line 3 call new_line with the act. pos. should facility the parameter count be located at the greater than one beginning of 'count' lines 4 call new_line with the default should facility count not given a be one value A-5 TEST SPECIFICATIONS A.5 NEW_PAGE A.5.1 REQUIREMENTS MET BY TEST This test specification satisfies the moving to a new page requirement for the scroll_mode terminal. A.5.2 DESCRIPTION OF TEST The test shall include moving the active position to a new page from the current active position on the scroll mode terminal. Typically the new page operation is a form feed but the user can tailor this to be anything he needs by describing it in the TCF. A.5.3 ASSUMPTIONS The scroll_mode terminal must be opened prior to the test. A.5.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 call new_page from the active position facility the beginning, end, should move to the and some internal beginning of the position on the line next page 2 call new_page after what is written to facility altering the virtual the virtual display display by writing should be shown on something at the act. the actual display pos. because new_page does a implicit call on update_line 3 call new_page with 'count' number of facility the parameter count new pages should be greater than one brought issued 4 call new_page with the default should facility count not given a be one value A-6 TEST SPECIFICATIONS A.6 PUT A.6.1 REQUIREMENTS MET BY TEST This test specification satisfies the writing characters and strings to the display requirement for the scroll_mode terminal. A.6.2 DESCRIPTION OF TEST The test shall include writing various strings and characters to the display. A.6.3 ASSUMPTIONS The scroll_mode terminal must be opened prior to the test. 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 call put with a after an update_ facility single char line is called the char written should appear on the actual screen with the act. pos. just past the char 2 call put with a after update_line is facility string which does not called the string exceed the line length written should appear on the actual screen with the act. pos. just past the string A-7 TEST SPECIFICATIONS 3 call put with a string after update_line is facility which when written called the string will will exceed the max appear but anything line length written past the max line length will be lost, the act. pos. should be at the last char written A-8 TEST SPECIFICATIONS A.7 GET A.7.1 REQUIREMENTS MET BY TEST This test specification satisfies the reading characters and strings from the keyboard requirement for the scroll_mode terminal. A.7.2 DESCRIPTION OF TEST The test shall include an explicit call on get to make sure that what we type from the keyboard is the only thing that the next call on get will see. We will then enter various combinations of characters and function keys and see if the get returns our input correctly. A.7.3 ASSUMPTIONS The scroll_mode terminal must be opened prior to the test. 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 call get after typing the string should facility a series of chars with match the typed no embedded function input and last keys, write out the should match the string returned and length of the string the parameter last A-9 TEST SPECIFICATIONS 2 call get after typing last should be 0. facility several function keys the value returned with no embedded chars, from fuction_count call function_count to should equal the determine how many keys number of keys pres- were pressed, call sed, function_key function_key to get the should return the actual key pressed actual key pressed (you must call function- _key 'function_count' times.) 3 call get after typing last should equal facility, some chars and function the number of chars keys intermixed, repeat typed. function_count the procedure of the should equal the num- previous test ber of function keys pressed, calls on function_key should re- turn the key pressed and the previous_position in the string 4 call get after typing last should be 0 and facility nothing at the function_count should keyboard be 0 5 call get with a a timeout should occur facility reachable timeout and the procedure value and do not type should return anything for at least that length of time A-10 TEST SPECIFICATIONS A.8 BELL A.8.1 REQUIREMENTS MET BY TEST This test specification satisfies the ringing the bell requirement for the scroll_mode terminal. A.8.2 DESCRIPTION OF TEST The test shall include an attempt to ring the terminal's bell as described in the TCF. A.8.3 ASSUMPTIONS The scroll_mode terminal must be opened prior to the test. 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 call bell the terminal's bell facility should ring. (The user can tailor this as he wishes). A-11 TEST SPECIFICATIONS TEST SPECIFICATIONS FOR THE PAGE MODE TERMINAL A.9 SET_TAB A.9.1 REQUIREMENTS MET BY TEST This test specification satisfies the tab stop setting requirement for the page_mode terminal. A.9.2 DESCRIPTION OF TEST The test shall include making a call on set_tab followed by a call on update_line. The call on set_tab should position a tab stop at the current active position on the virtual display. The tab stop should remain in the same column on succeeding lines. We will then make a call on tab after a new_line has been issued to see if the set_tab worked properly. A.9.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. 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 call on set_tab tab stop set at facility active position 2 call on set_tab tab stop remains facility while active position no apparent is on a tab stop action A-12 TEST SPECIFICATIONS A.10 CLEAR_TAB A.10.1 REQUIREMENTS MET BY TEST This test specification satisfies the clear tab stop requirement for the page_mode terminal. A.10.2 DESCRIPTION OF TEST The test shall include removing a tab stop at the active position on the page mode terminal. A.10.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.10.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 call on clear_tab tab stop removed facility while active position is on a tab stop 2 call on clear_tab no apparent facility while active position action is not on a tab stop A-13 TEST SPECIFICATIONS A.11 TAB A.11.1 REQUIREMENTS MET BY TEST This test specification satisfies the moving to a tab stop requirement for the page_mode terminal. A.11.2 DESCRIPTION OF TEST The test shall include moving the active position to a tab stop from the current active position on the page mode terminal. A.11.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.11.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 call on tab with no no operation will facility tab stops set occur 2 call on tab with a the act. pos. should facility tab stop remaining be moved to this tab to the right of the stop active position 3 call on tab while the the act. pos should facliity act. pos. is to the be positioned at the right of a tab stop first tab stop on the next line 4 call on tab with a the active postion facility the parameter count will be moved the spec- equal to some number ified number of tab greater than one stops A-14 TEST SPECIFICATIONS A.12 NEW_LINE A.12.1 REQUIREMENTS MET BY TEST This test specification satisfies the moving to a new line requirement for the page_mode terminal, and the setting tab stops requirement. A.12.2 DESCRIPTION OF TEST The test shall include moving the active position to a new line from the current active position on the page mode terminal. Moving to a new line in the page mode terminal will consist of a call on set position and erase_in_line or a call on insert_line to move to a new line. A.12.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.12.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 move to a new line the active position facility from the beginning, should move to the end, and some internal beginning of the position on the line new line 2 move to a new line the tab stop should facility with a tab stop set remain on the the on the line next line, new_ line postions the act. pos. at the beginning of the next line A-15 TEST SPECIFICATIONS A.13 NEW_PAGE A.13.1 REQUIREMENTS MET BY TEST This test specification satisfies the moving to a new page requirement for the page_mode terminal. A.13.2 DESCRIPTION OF TEST The test shall include moving the active position to a new page from the current active position on the page mode terminal. The new_page requirement for the page_mode terminal is fulfilled by calling set_position (1, 1) and erase_display. A.13.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.13.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 a new page from the active position facility the beginning, end, should move to the and some internal beginning of the position on the line next page A-16 TEST SPECIFICATIONS A.14 PUT A.14.1 REQUIREMENTS MET BY TEST This test specification satisfies the writing characters and strings to the display requirement for the page_mode terminal. A.14.2 DESCRIPTION OF TEST The test shall include writing various strings and characters to the display. A.14.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.14.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 call put with a after an update_ facility single char line is called the char written should appear on the actual screen with the act. pos. just past the char 2 call put with a after update_line is facility string which does not called the string exceed the line length written should appear on the actual screen with the act. pos. just past the string A-17 TEST SPECIFICATIONS 3 call put with a string after update_line is facility which when written called the string will will exceed the max appear but anything line length written past the max line length will be lost, the act. pos. should be at the last char written A-18 TEST SPECIFICATIONS A.15 GET A.15.1 REQUIREMENTS MET BY TEST This test specification satisfies the reading characters and strings from the keyboard requirement for the page_mode terminal. A.15.2 DESCRIPTION OF TEST The test shall include an explicit call on get to make sure that what we type from the keyboard is the only thing that the next call on get will see. We will then enter various combinations of characters and function keys and see if the get returns our input correctly. A.15.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.15.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 call get after typing the string should facility a series of chars with match the typed no embedded function input and last keys, write out the should match the string returned and length of the string the parameter last A-19 TEST SPECIFICATIONS 2 call get after typing last should be 0. facility several function keys the value returned with no embedded chars, from fuction_count call function_count to should equal the determine how many keys number of keys pres- were pressed, call sed, function_key function_key to get the should return the actual key pressed actual key pressed (you must call function- _key 'function_count' times.) 3 call get after typing last should equal facility some chars and function the number of chars keys intermixed, repeat typed. function_count the procedure of the should equal the num- previous test ber of function keys pressed, calls on function_key should re- turn the key pressed and the previous_position in the string 4 call get after typing last should be 0 and facility nothing at the function_count should keyboard be 0 5 call get with a a timeout should occur facility reachable timeout and the procedure value and do not type should return anything for at least that length of time A-20 TEST SPECIFICATIONS A.16 DELETE_CHARACTER A.16.1 REQUIREMENTS MET BY TEST This test specification satisfies the delete character from display requirement and the writing to the display requirements for the page_mode terminal. A.16.2 DESCRIPTION OF TEST The test shall include several calls on put to get some lines of input on the display. We will then position the cursor in various spots and delete some characters. A.16.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.16.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 call put with several the input lines facility lines of input, then should appear on call update_screen the actual display 2 call delete_character the characters at facility from various positions each act. pos. should on the display, then be removed from the call update screen actual display A-21 TEST SPECIFICATIONS 3 call delete_charater the chars deleted facility with a parameter great- include the char the er than one, then call act. pos. is on and update screen all chars to the right up to the parameter count, the chars to the right of the deleted chars are shifted left and the line fills with blanks from the right 4 call with the parameter the line should be facility count greater than deleted from the act. the number of remaining pos. to the end of the chars on the line, then line, blanks fill from call update screen the right 5 call delete_character an error should occur, facility with a negative sub- only a positive value script is allowed as a para- meter A-22 TEST SPECIFICATIONS A.17 DELETE_LINE A.17.1 REQUIREMENTS MET BY TEST This test specification satisfies the delete line from display requirement and the writing to the display requirements for the page_mode terminal. A.17.2 DESCRIPTION OF TEST The test shall include several calls on put to get some lines of input on the display. We will then position the cursor in various spots and delete some lines. A.17.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.17.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 call put with several the input lines facility lines of input, then should appear on call update_screen the actual display 2 call delete_line with the line the act. facility the act. pos. in the pos. was on should middle, at the end, be deleted and the and at the beginning. cursor will be at the then call update screen beginning of the next line 3 call delete_line from the top line should facility the top of the screen, be deleted, the lines call update screen below it will shift up, a blank line will fill in the bottom A-23 TEST SPECIFICATIONS 4 call delete_line from the line containing facility the middle of the the act. pos. should screen, then call be deleted, the foll- update screen owing lines should shift up and the cursor will be placed at the beginning of the next line 5 call delete_line from the last line should facility the last line on the be deleted, and the display, then update cursor will be at the screen beginning of the next line (blank) 6 call delete_line with the number of lines facility a parameter greater specified should be than one, move the act. deleted from the pos. toward the bottom first act. pos. on- of the screen call ward, then the screen delete_line again should be blank from with count greater the place the act. than one and more than pos. was postioned the number of lines to the bottom of the left, update screen screen A-24 TEST SPECIFICATIONS A.18 ERASE_IN_DISPLAY A.18.1 REQUIREMENTS MET BY TEST This test specification satisfies the erasing charaters from the display requirement for the page_mode terminal, along with the writing characters to the display requirement. A.18.2 DESCRIPTION OF TEST The test shall include several calls on put to get some lines of input on the display. We will then position the cursor in various spots and erase some characters from the display. A.18.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.18.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 call put with several the input lines facility lines of input, then should appear on call update_screen the actual display 2 position the act. pos. the entire screen facility somewhere in the middle should be erased, of the screen. call the cursor should erase_in_display with not move from the a parameter of all_- active position positions, update screen 3 get some more data on the display should facility the actual display and be erased from the call erase_in_display top of the screen with the act. pos. to, but not including, somewhere in the middle the act. pos. of the screen, erase the display from the top to the act. pos., call update screen A-25 TEST SPECIFICATIONS 4 call erase_in_display the remaining data facility with a parameter to on the display erase from the act. should be erased, pos. to the end of the cursor should the virtual display, be left alone erase from the position left by the previous test, update screen 5 try erasing from the nothing should act. pos. to the end happen of the display when the act. pos. is at the end of screen A-26 TEST SPECIFICATIONS A.19 ERASE_IN_LINE A.19.1 REQUIREMENTS MET BY TEST This test specification satisfies the erasing charaters between specific positions on the display requirement for the page_mode terminal, along with the writing characters to the display requirement. A.19.2 DESCRIPTION OF TEST The test shall include several calls on put to get some lines of input on the display. We will then position the cursor in various spots and erase some characters from the display. A.19.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.19.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 call put with several the input lines facility lines of input, then should appear on call update_screen the actual display 2 position the act. pos. the entire line facility somewhere in the middle should be erased, of the line. call the cursor should erase_in_line with not move from the a parameter of all_- active position positions, update screen 3 move the act. pos. the display should facility to another line on the be erased from the display, call erase_in_ beginning of the line line with the act. pos. to, but not including, somewhere in the middle the act. pos. of the line, erase the display from the beginning to the act. pos., update screen A-27 TEST SPECIFICATIONS 4 call erase_in_display the remaining data facility with a parameter to on the line erase from the act. should be erased, pos. to the end of the cursor should a line on the display, be left alone erase from the position left by the previous test, update screen 5 try erasing from the nothing should act. pos. to the end happen of the line when the act. pos. is at the end of line A-28 TEST SPECIFICATIONS A.20 INSERT CHARACTERS A.20.1 REQUIREMENTS MET BY TEST This test specification satisfies the inserting characters onto the display requirement for the page_mode terminal, along with the writing characters to the display requirement. A.20.2 DESCRIPTION OF TEST The test shall include several calls on put to get some lines of input on the display. We will then position the cursor in various spots and insert some characters to the display. A.20.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.20.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 call put with several the input lines facility lines of input, then should appear on call update_screen the actual display 2 position the act. pos. the chars type in at facility in the middle of one of the keyboard should the lines with data on be located immediately it. call enter_insert_- before the act. pos. mode, then type some in appropriate order, chars in from the key- the act. pos. moves board, update screen right the number of chars written A-29 TEST SPECIFICATIONS 3 position the act. pos. the chars previous facility at the end of a line, to the max line length type enough chars to will be inserted, the make the line exceed ones past this point the max line length, are lost update screen 4 position the act. pos. no chars should be back in the middle of written to the a line, call exit_- screen, the act. pos. insert_mode, try should not move typing in some chars, update screen A-30 TEST SPECIFICATIONS A.21 INSERT_LINE A.21.1 REQUIREMENTS MET BY TEST This test specification satisfies the inserting lines onto the display requirement for the page_mode terminal, along with the writing characters to the display requirement. A.21.2 DESCRIPTION OF TEST The test shall include several calls on put to get some lines of input on the display. We will then position the cursor in various spots and insert some lines in the display. A.21.3 ASSUMPTIONS The page_mode terminal must be opened prior to the test. A.21.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 call put with several the input lines facility lines of input, then should appear on call update_screen the actual display 2 position the act. pos. blank lines should facility on the top, middle, and be inserted where bottom of the display, ever the act. pos. call insert_line from was when insert line these vaious spots, was called, the cursor update screen will be at the begin- ning of the blank line corresponding with the last call on insert_- line, lines below the inserted line are pushed downward A-31 TEST SPECIFICATIONS 3 call insert_line with there should be as facility a parameter greater blank lines specified than one, update screen in the call inserted into the display, the cursor will be located at the first blank line inserted, any lines pushed off the display are lost A-32 TEST SPECIFICATIONS A.22 SELECT_GRAPHIC_RENDITION A.22.1 REQUIREMENTS MET BY TEST This test specification satisfies the setting graphic rendition requirement for the form_mode terminal, along with the writing characters and inserting characters to the display requirements. A.22.2 DESCRIPTION OF TEST The test shall include several calls on put to get some lines of input on the display. We will then change the rendition of the display and check to see if it is done properly. A.22.3 ASSUMPTIONS The form_mode terminal must be opened prior to the test. A.22.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 call put with several the input lines facility lines of input, then should appear on call update_screen the actual display 2 position the act. pos. the chars entered facility in the middle of a line should appear in of input, call select_ reverse image, usally graphic_rendition with defined as dark chars reverse_image, call on light background, put with a string cursor should of data, update screen again be located past the inserted chars 3 call select_graphic_- the string should be facility rendition with the same written with the same value that is presently rendition as the other active, write a string chars, the act. pos. to the display, update will be just past the screen string written A-33 TEST SPECIFICATIONS A.23 BELL A.23.1 REQUIREMENTS MET BY TEST This test specification satisfies the ringing the bell requirement for the scroll_mode terminal. A.23.2 DESCRIPTION OF TEST The test shall include an attempt to ring the terminal's bell as described in the TCF. A.23.3 ASSUMPTIONS The scroll_mode terminal must be opened prior to the test. A.23.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 call bell the terminal's bell facility should ring. (The user can tailor this as he wishes). A-34 TEST SPECIFICATIONS TEST SPECIFICATIONS FOR THE FORM MODE TERMINAL A.24 DEFINE_QUALIFIED_AREAS A.24.1 REQUIREMENTS MET BY TEST This test specification satisfies the defining qualified areas on the display requirement and the move by tab stops requirement for the form_mode terminal. A.24.2 DESCRIPTION OF TEST The test shall include defining several qualified areas with various characteristics and showing that they exist with the characteristics described. A.24.3 ASSUMPTIONS The form_mode terminal must be opened prior to the test. A.24.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 call define_qualified_- Each qualified area facility area with various defined should exist parameters in various and have the charact- places on the display, eristics specified activate form 2 try accessing a pro- Each individual test facility tected area, write to a should correctly unprotected area to show represent the char- that it's intensity is acteristics specified correct, check the in the call on define_ other parameters for qualified_area correctness, activate form A-35 TEST SPECIFICATIONS A.25 CLEAR_QUALIFIED_AREAS A.25.1 REQUIREMENTS MET BY TEST This test specification satisfies the clearing qualified areas on the display requirement and the move by tab stops requirement for the form_mode terminal. A.25.2 DESCRIPTION OF TEST The test shall include taking a form that exists and clearing several of the qualified areas. The previous qualified area to the one cleared should expand to fill the area cleared. The active position must be at the beginning of a qualified area for the area to be cleared. A.25.3 ASSUMPTIONS The form_mode terminal must be opened prior to the test. A.25.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 call clear_qualified_- the qualified area facility area with the active should be cleared position located at the from the form, the beginning of a qualified previous qualified area, position the area should now cursor above the cleared encompass the cleared area, tab to the next area qualified area, activate form 2 clear the first the area should be facility qualified area on the protected and set to display, activate form blank 3 clear a qualified area nothing will happen, with the act. pos. the area will still located in middle of exist the area, activate form A-36 TEST SPECIFICATIONS A.26 TAB A.26.1 REQUIREMENTS MET BY TEST This test specification satisfies the moving by tab stops on the display requirement for the form_mode terminal. The define qualified area requirement will also be satisfied within this test specification. A.26.2 DESCRIPTION OF TEST The test shall include taking a form that exists moving by tab stops to the next qualified area on the virtual display. Areas must be defined before this requirement can be tested properly. A.26.3 ASSUMPTIONS The form_mode terminal must be opened prior to the test. A.26.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 call tab with a qual- the cursor should facility ified area defined move to the begin- in front of the act. ning of the next pos., activate form qualified area 2 call tab when at the the cursor should be facility last qualified area on at the first quali- a line, activate form fied area on the next line 3 call tab when at the the cursor should be facility last qualified area on at the first quali- the form, activate form fied area of the form 4 call tab with a para- the cursor should be facility meter greater than one, positioned the spec- activate form ified number of quali- fied areas toward the end of the display A-37 TEST SPECIFICATIONS A.27 GET A.27.1 REQUIREMENTS MET BY TEST This test specification satisfies the reading characters and strings from the display requirement for the form_mode terminal. A.27.2 DESCRIPTION OF TEST The test shall include reading characters from the display as single characters and strings. A.27.3 ASSUMPTIONS The form_mode terminal must be opened prior to the test. A.27.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 read a character from check to see that facility the act. pos., move the the get reads the act. pos. to a new qual- data correctly, the ified area and read a act. pos. should be string, activate form located just past the last char read A-38 TEST SPECIFICATIONS A.28 ERASE_AREA A.28.1 REQUIREMENTS MET BY TEST This test specification satisfies the erasing between specified areas on the display requirement for the form_mode terminal. Also displayed is the moving by tab stops requirement. A.28.2 DESCRIPTION OF TEST The test shall include erasing several qualified areas on the virtual display. A.28.3 ASSUMPTIONS The form_mode terminal must be opened prior to the test. A.28.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 call tab to get to the area should be facility the beginning of erased and filled a qualified area, with blanks call erase_area, activate form 2 call set_position to the area from the facility move the act. pos. to act. pos. to the end the middle of a quali- of the qualified area fied area, call erase_- should be erased and area, activate form filled with blanks A-39 TEST SPECIFICATIONS A.29 ERASE_DISPLAY A.29.1 REQUIREMENTS MET BY TEST This test specification satisfies the erasing between specified areas on the display requirement for the form_mode terminal. Also displayed is the moving by tab stops requirement. A.29.2 DESCRIPTION OF TEST The test shall include erasing several qualified areas on the virtual display. A.29.3 ASSUMPTIONS The form_mode terminal must be opened prior to the test. A.29.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 call tab to get to the entire display facility a qualified area, should be erased, call erase_display, the cursor should be call tab, activate form positioned at the top left corner of the display A-40 TEST SPECIFICATIONS A.30 ACTIVATE_FORM A.30.1 REQUIREMENTS MET BY TEST This test specification satisfies the activating a form requirement for the form_mode terminal. The define qualified area requirement and the retrieving the function key which signaled a full form are also exhibited. A.30.2 DESCRIPTION OF TEST The test shall include activating a form, editting that form, and terminating that form. Control will return to the user's program. A.30.3 ASSUMPTIONS The form_mode terminal must be opened prior to the test. A.30.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 define several quali- the actual display facility fied areas on the should look exactly virtual display, call like the virtual activate_form display, the cursor should be at the first editing position of the form 2 perform local editing, carriage returns facility, this shall include move to the next line, usability using carrage returns, tab moves to the next tabs, arrow keys, del- unprotected area, etes, and function keys arrow keys perform thier function, del char deletes under the cursor( chars shift left ) function keys return to to the user's program A-41 TEST SPECIFICATIONS 3 write to a protected rings the bell( as facility area defined in the TCF ) 4 press a function key, control should return facility call terminatin_key to the user's program, termination_key will return the function key pressed to return to the user's program A-42 TEST SPECIFICATIONS A.31 PUT A.31.1 REQUIREMENTS MET BY TEST This test specification satisfies the writing characters and strings to the display requirement for the form_mode terminal. A.31.2 DESCRIPTION OF TEST The test shall include writing several strings and characters to the display. A.31.3 ASSUMPTIONS The form_mode terminal must be opened prior to the test. A.31.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 call put with string, the string should facility activate form appear in the display at the position the act. pos. was located when put was called 2 call put with a string the remaining part of facility which will exceed the the string will wrap maximum allowed line to the next line length, activate form 3 call put with a string the screen should facility which will run off the also, the remaining display, activate form part of the string will appear in the top of the display A-43 APPENDIX B MATRICES This appendix contains two cross reference matrices that show the relationship between the test specifications in Appendix A and the requirements from the Proposal to Design and Implement an Ada Virtual Terminal[TI84]. The Test Specification Matrix lists the test specifications in order and shows which requirements are satisfied with each test specification. In addition, the Test Specification Matrix contains two columns for check off and comments to fill in as the test specifications are fulfilled. The second matrix, the Requirements Cross Reference Matrix, provides a quick reference of the location where each requirement is satisfied within this document. The acceptance requirements from the proposal document [TI84] are listed along with the test specifications that satisfy each requirement and the specific section where the procedure is described. B-1 MATRICES TEST SPECIFICATION MATRIX ------------------------------------------------------------------ | TEST SPEC | REQUIREMENTS | CHECK | COMMENTS | |============|================|=======|==========================| | A.1 | 4, 6 | | | |------------|----------------|-------|--------------------------| | A.2 | 4, 5, 6 | | | |------------|----------------|-------|--------------------------| | A.3 | 4, 6 | | | |------------|----------------|-------|--------------------------| | A.4 | 4, 6, 7 | | | |------------|----------------|-------|--------------------------| | A.5 | 8 | | | |------------|----------------|-------|--------------------------| | A.6 | 1 | | | |------------|----------------|-------|--------------------------| | A.7 | 2 | | | |------------|----------------|-------|--------------------------| | A.8 | 3 | | | |------------|----------------|-------|--------------------------| | A.9 | 12, 14 | | | |------------|----------------|-------|--------------------------| | A.10 | 12, 13, 14 | | | |------------|----------------|-------|--------------------------| | A.11 | 12, 14 | | | |------------|----------------|-------|--------------------------| | A.12 | 12, 14, 15 | | | |------------|----------------|-------|--------------------------| | A.13 | 16 | | | |------------|----------------|-------|--------------------------| | A.14 | 9 | | | |------------|----------------|-------|--------------------------| B-2 MATRICES |------------|----------------|-------|--------------------------| | A.15 | 10 | | | |------------|----------------|-------|--------------------------| | A.16 | 9, 17 | | | |------------|----------------|-------|--------------------------| | A.17 | 9, 18 | | | |------------|----------------|-------|--------------------------| | A.18 | 9, 19 | | | |------------|----------------|-------|--------------------------| | A.19 | 9, 20 | | | |------------|----------------|-------|--------------------------| | A.20 | 9, 21 | | | |------------|----------------|-------|--------------------------| | A.21 | 9, 22 | | | |------------|----------------|-------|--------------------------| | A.22 | 9, 21, 23 | | | |------------|----------------|-------|--------------------------| | A.23 | 11 | | | |------------|----------------|-------|--------------------------| | A.24 | 24, 26, 28 | | | |------------|----------------|-------|--------------------------| | A.25 | 25, 26, 28 | | | |------------|----------------|-------|--------------------------| | A.26 | 24, 26, 28 | | | |------------|----------------|-------|--------------------------| | A.27 | 29 | | | |------------|----------------|-------|--------------------------| | A.28 | 26, 27, 28 | | | |------------|----------------|-------|--------------------------| | A.29 | 26, 27 | | | |------------|----------------|-------|--------------------------| | A.30 | 24, 28, 31 | | | |------------|----------------|-------|--------------------------| | A.31 | 30 | | | ------------------------------------------------------------------ B-3 MATRICES REQUIREMENTS CROSS REFERENCE MATRIX The requirements which are located in the following matrix are taken from the Proposal to Design and Implement an ANSI X3.64 Compatiable Virtual Terminal in Ada, section 2.4.1 TEST PROCEDURE REQ. # REQUIREMENT SPECIFICATIONS SECTION ====== =========== ============== ========= 1 Writing chars and strings to A.6 3.3.3.6 the display for the scroll_mode terminal 2 Reading chars and strings from A.7 3.3.3.7 the keyboard for the scroll_ mode terminal 3 Ringing the terminals bell for A.8 3.3.3.8 the scroll_mode terminal 4 Setting tab stops for the A.1 3.3.3.1 scroll_mode terminal 5 Clearing tab stops for the A.2 3.3.3.2 scroll_mode terminal 6 Moving to a tab stop for the A.3 3.3.3.3 scroll_mode terminal 7 Moving to a new line for the A.4 3.3.3.4 scroll_mode terminal 8 Moving to a new page for the A.5 3.3.3.5 scroll_mode terminal 9 Writing characters and strings A.14 3.3.3.14 to the display for the page_mode terminal B-4 MATRICES 10 Reading characters and strings A.15 3.3.3.15 from the keyboard for the page_mode terminal 11 Ringing the terminals bell for A.23 3.3.3.16 the page_mode terminal 12 Setting tab stops for the A.9 3.3.3.9 page_mode terminal 13 Clearing tab stops for the A.10 3.3.3.10 page_mode terminal 14 Moving to a tab stop for the A.11 3.3.3.11 page_mode terminal 15 Moving to a new line for the A.12 3.3.3.12 page_mode terminal 16 Moving to a new page for the A.13 3.3.3.13 page_mode terminal 17 Deleting characters from the A.16 3.3.3.17 display for the page_mode terminal 18 Deleting lines from the display A.17 3.3.3.18 for the page_mode terminal 19 Erasing characters from the A.18 3.3.3.19 display for the page_mode terminal 20 Erasing between specific positions A.19 3.3.3.20 within lines for the page_mode terminal 21 Inserting characters onto the A.20 3.3.3.21 display for the page_mode terminal 22 Inserting lines onto the display A.21 3.3.3.22 for the page_mode terminal 23 Setting the graphic rendition on A.22 3.3.3.23 the display for the page_mode terminal B-5 MATRICES 24 Defining qualified areas on the A.24 3.3.3.24 display for the form_mode terminal 25 Clearing qualified areas on the A.25 3.3.3.25 display for the form_mode terminal 26 Moving by tab stops on the A.26 3.3.3.26 display for the form_mode terminal 27 Erasing between specific positions A.28, 3.3.3.27 on the display for the form_mode A.29 terminal 28 Activating a form for user fill A.30 3.3.3.30 in for the form_mode terminal 29 Reading characters and strings A.27 3.3.3.28 from the display buffer for the form_mode terminal 30 Writing characters and strings A.31 3.3.3.29 to the display buffer for the form_mode terminal 31 Retrieving the function key A.30 3.3.3.30 which signaled a full form for the form_mode terminal B-6 APPENDIX C GLOSSARY _____ actor An operation on an object that changes the state, structure, or value of the object. ____ ACSL Advanced Computer Systems Laboratory, Texas Instruments ___ AIE Ada Integrated Environment ___ AIM APSE Interactive Monitor ___ _______ ___________ ____ ___ AIM command interpreter (AIM CI) The AIM subsystem concerned with the interpretation of user commands. The user commands include those specified directly to the AIM CI by the user as well as special key sequences (such as the Switch-to-Monitor key). ___ ______ AIM driver The AIM subsystem concerned with initializing and controlling the actual execution of the AIM program. ___ _______ _______ AIM program manager The AIM subsystem concerned with the invocation and control of subordinate APSE programs. ___ _________ _______ AIM structure manager The AIM subsystem concerned with the maintenance of the relationships between images, windows, viewports, viewport headers, and special AIM modes. ___ _______ ________ AIM virtual terminal The AIM subsystem concerned with the manipulation and interrogation of display terminals. C-1 GLOSSARY ___ ALS Ada Language System ____ APSE Ada Programming Support Environment ____ ___ APSE CLP The APSE Command Language Processor is the program within the host APSE concerned with the interpretation of user commands at the APSE level. ____ _______ APSE program ____ ____ A program that can be executed in the hosting APSE and uses only _____ ________ ________ KAPSE supplied services to perform its function. ____ area A set of adjacent character positions in a visual display that are not necessarily on the same line. _________ character A member of a set of elements that is used for the organization, control, or representation of data. _________ ____ character echo The act of re-transmitting a character immediately upon receipt of it back to the entity that originally transmitted it. _________ _______ ______ character imaging device A device that gives a visual representation of data in the form of graphic symbols using any technology, such as cathode ray tube or printer. _________ ______ character stream An unbounded sequence of ASCII characters. _________ ______ character string A bounded sequence of ASCII characters. ____ CPCI Computer Program Configuration Item. ________ ____ database file A standard file in the APSE database. _______ display The area for visual presentation of data on a character imaging device. _______ ________ display terminal A data communications device composed of a keyboard and a display screen (usually a cathode ray tube). C-2 GLOSSARY ________ ________ hardcopy terminal A data communications device composed of a keyboard and a printer. _____ image An image is an analog of the physical display device. The image is the entity that is mapped onto the display. Given a number of user defined images, only one at a time can be mapped onto the display. The rest exist and are updated asynchronously but are not mapped onto the display until the user requests it. _________ interface The place at which independent systems meet and act on or communicate with each other. _____ KAPSE Kernel Ada Programing Support Environment. ________ keyboard The keyboard is the physical input device. ____ line A line is a set of adjacent character positions in a visual display that have the same vertical position. ____ NOSC Naval Ocean Systems Center ___ pad A pad is a complete history of window activity that transpires from the initial invocation of pad mode until it is terminated by the user or the window is destroyed. This includes the input to the APSE program from the user through the keyboard as well as the output to the display from the AIM and any program initiated by the AIM. ____ pipe A logical connection between an output file of one program and an input file of another program. ___ PPS Program Performance Specification ______ screen The area for visual presentation of data on any type of character imaging device, including printer and cathode ray tube device. ______ ____ ________ scroll mode terminal A display terminal that presents data by moving all the graphic symbols of the screen in one direction to make room for new data. C-3 GLOSSARY ________ Selector An operation on an object that returns a value or attribute and makes no alteraction of the state, structure, or value of the object. _________________ ___ Switch-to-Monitor key The keyboard sequence that causes the AIM to perform the Switch-to-Monitor function. ____ task An Ada program unit that operates in parallel with other program units. ________ terminal A data communications device consisting of a keyboard and a character imaging device. ________ ____________ ____ Terminal Capabilities File he Terminal Capabilities File is an APSE database file which contains mappings from logical computer terminal characteristics to specific computer terminal characteristics. The Terminal Capabilities File can contain information that supports many different terminal types and makes. ________ transmit To send data as a data stream for purposes of information interchange. ___________ ____ ______ transmitted data stream The stream of bit combinations sent by a character imaging device when it is induced to transmit for purposes of information interchange. ____ ________ user terminal The terminal with which a user interacts in order to communicate with an APSE program. ________ viewport A viewport is the portion of the window displayed in the image. ________ ______ viewport header A viewport header is a single optional highlighted line located at the top of a viewport. ______ window A window is an analog of the APSE program's view of the terminal. C-4