Good Programming Techniques. III. Non—Computer Based Testing

John B. Slater
Additional contact information
John B. Slater: University of Bath, Bath University Computing Service

A chapter in Supercomputational Science, 1990, pp 45-54 from Springer

Abstract: Abstract In the early days of computing the programmer designer, numerical expert, etc spent a good deal of time checking through every single facet of a program before it was let near the computer. Computer time was so precious that any amount of human effort was considered to be worthwhile to avoid a wasted run on the machine. Dry running or desk checking — the technique of “playing computer” to real data — was an expected weapon in the armoury of all programmers, not merely as a means of avoiding bugs, but as the main means of finding them after an unsuccessful run. This phenomenon can be reproduced if you look at current GCSE syllabi, especially as taught at those few schools still relying on batch services for their computing.

Keywords: Integer Variable; Unit System; Boolean Operator; Check List; Reference Variable (search for similar items in EconPapers)
Date: 1990
References: Add references at CitEc
Citations:

There are no downloads for this item, see the EconPapers FAQ for hints about obtaining it.

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:spr:sprchp:978-1-4684-5820-6_6

Ordering information: This item can be ordered from
http://www.springer.com/9781468458206

DOI: 10.1007/978-1-4684-5820-6_6

Access Statistics for this chapter

More chapters in Springer Books from Springer
Bibliographic data for series maintained by Sonal Shukla () and Springer Nature Abstracting and Indexing ().