NBS Minimal BASIC Test Programs: Version 2, User's Manual, Volume 13U.S. Department of Commerce, National Bureau of Standards, 1980 |
From inside the book
Results 1-5 of 9
Page 11
... possible inputs to the system under investigation implementation ) and see whether the results are in accord with the specifications for that system ( the language standard ) . behavior ( the A Thus , successful results of the tests are ...
... possible inputs to the system under investigation implementation ) and see whether the results are in accord with the specifications for that system ( the language standard ) . behavior ( the A Thus , successful results of the tests are ...
Page 15
... possible , in the case of failure of a test . The rest of this section describes the strategy we ultimately adopted , and its relationship to conformance and to interpretation by the user of the programs . 4.1 Testing Features Before ...
... possible , in the case of failure of a test . The rest of this section describes the strategy we ultimately adopted , and its relationship to conformance and to interpretation by the user of the programs . 4.1 Testing Features Before ...
Page 16
... possible , consistent with adequate testing . No program exceeds 300 lines in length . The programs print many informative messages which may be changed without affecting the outcome of the tests . If your implementation cannot handle a ...
... possible , consistent with adequate testing . No program exceeds 300 lines in length . The programs print many informative messages which may be changed without affecting the outcome of the tests . If your implementation cannot handle a ...
Page 19
... possible , therefore , that a standard program , executing on two different standard - conforming processors , using the same data , could cause an exception in one implementation and not in the other . The tests attempt to force the ...
... possible , therefore , that a standard program , executing on two different standard - conforming processors , using the same data , could cause an exception in one implementation and not in the other . The tests attempt to force the ...
Page 22
... possible enhancements , also tried to assist the user in confirming what the actual processor behavior is , so that it may be checked against the documentation . For example , the program that tests whether the implementation accepts ...
... possible enhancements , also tried to assist the user in confirming what the actual processor behavior is , so that it may be checked against the documentation . For example , the program that tests whether the implementation accepts ...
Other editions - View all
Common terms and phrases
8.4 PROGRAM NUMBER algorithm allows ANSI BASIC ANSI standard argument assignment Backus-Naur Form BASIC Test Programs behavior computer languages correctly decimal digits defined division by zero error programs ERROR REFS error tests Exception Handling exception report exception tests execution FOR-blocks FOR-STATEMENT FORTRAN functional group GOTO handling implementation accepts IMPLEMENTATION CONFORMANCE implementation of BASIC implementation-defined features informative tests input-reply interpretation language standard line number machine infinity measure Minimal BASIC Test non-fatal exceptions non-standard construction non-standard programs Note NUMERIC CONSTANTS NUMERIC EXPRESSIONS ON-GOTO operations OPTION BASE pass/fail message PASSES else processor passing or failing PBASIC processor FAILS processor PASSES program conformance program is standard program output programming language recovery procedure reject REM statement requirements RND FUNCTION rules sample output self-checking semantic meaning significand simple source code specified Standard Capabilities standard program syntax test fails TEST PASSED test sequence test system UNDERFLOW University of Kent USER-DEFINED FUNCTION Version zeros