1
0
mirror of synced 2026-02-03 07:30:58 +00:00
Files
Interlisp.medley/internal/test/README.TEDIT
2020-12-16 18:21:28 -08:00

10 lines
7.5 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Originally from .read-me-first
Notes from Envos directories
Note I/O was a problem (/ in directory
Maiko.
Subdirs ARs, AUTO, Aux, HAND, OBSOLETE
in Maiko:
STACKHAX (has CHECKSTACKSPACE, seems to get tangled up in it's own stack
STACKTAKESHI (seems to cause a stack overflow on opurpose, which leaves stack clean enough that URAID hard-reset recovers from. Suspect timeouts aren't correct
BAD-XREF (no compiled file)
display.cl (says "from Texas Instruments")
Maiko>OBSOLETE
AREF-TESTER (compiled OK)
ARRAY-TESTER.TEST
FLOAT-TESTER (doesn't compile, error on BIGNUM)
MAIKO-UNWIND-TESTS
TESTER (compiled OK)
unwindtest
xclopcodetests
Tools> (need to get working first)
XAIS Testing Directory Structure
Special Files: For saving overall-testing information
Information {Eris}<Test>, files named .name, e.g. ª.read-me-firstº , this file.
Procedures {Eris}<Test>Admin> for overall procedure files, rather than specific test plans or scripts
Results {Eris}<Test>ARs> for the results of AR test-case regression runs.
Tools {Eris}<Test>Tools> for general-purpose files like do-test or do-test-menu.
Language: The Interlisp & Common Lisp languages, interpreters, compilers
Plans {Eris}<Test>Language>Plans>
Results {Eris}<Test>Language>Logs>
Auto
Test-Files {Eris}<Test>Language>Auto>
Aux-Files {Eris}<Test>Language>Auto-Aux>
Hand
Scripts {Eris}<Test>Language>Hand>
Aux-Files {Eris}<Test>Language>Hand-Aux>
IO: Streams, Windows
Plans {Eris}<Test>IO>Plans>
Results {Eris}<Test>IO>Logs>
Auto
Test-Files {Eris}<Test>IO>Auto>
Aux-Files {Eris}<Test>IO>Auto-Aux>
Hand
Scripts {Eris}<Test>IO>Hand>
Aux-Files {Eris}<Test>IO>Hand-Aux>
Prog Environment: Exec, Code Editing, Debugging, Application Toolkits
[subsection: Exec, Debugger, Editors]
Plans {Eris}<Test>Env>subsection>Plans>
Results {Eris}<Test>Env>subsection>Logs>
Auto
Test-Files {Eris}<Test>Env>subsection>Auto>
Aux-Files {Eris}<Test>Env>subsection>Auto-Aux>
Hand
Scripts {Eris}<Test>Env>subsection>Hand>
Aux-Files {Eris}<Test>Env>subsection>Hand-Aux>
Library: Individual Modules
[Module name]
Plans {Eris}<Test>Library>module>Plans>
Results {Eris}<Test>Library>module>Logs>
Auto
Test-Files {Eris}<Test>Library>module>Auto>
Aux-Files {Eris}<Test>Library>module>Auto-Aux>
Hand
Scripts {Eris}<Test>Library>module>Hand>
Aux-Files {Eris}<Test>Library>module>Hand-Aux>
LispUsers: Repository for obsoleted library tests when modules are demoted
[Module name]
Plans {Eris}<Test>LispUsers>module>Plans>
Results {Eris}<Test>LispUsers>module>Logs>
Auto
Test-Files {Eris}<Test>LispUsers>module>Auto>
Aux-Files {Eris}<Test>LispUsers>module>Auto-Aux>
Hand
Scripts {Eris}<Test>LispUsers>module>Hand>
Aux-Files {Eris}<Test>LispUsers>module>Hand-Aux>
Applications: ªCustomer Applications" for stress-testing system or subsystems
[Application name]
Plans {Eris}<Test>Customer-Applications>application-name>Plans>
Results {Eris}<Test>Customer-Applications>application-name>Logs>
Auto
Test-Files {Eris}<Test>Customer-Applications>application-name>Auto>
Aux-Files {Eris}<Test>Customer-Applications>application-name>Auto-Aux>
Hand
Scripts {Eris}<Test>Customer-Applications>application-name>Hand>
Aux-Files {Eris}<Test>Customer-Applications>application-name>Hand-Aux>
[Subsystem, e.g. PCE]: One subdirectory per distinct product (PCE, Rooms, DEI, ...)
Plans {Eris}<Test>subsystem>Plans>
Results {Eris}<Test>subsystem>Logs>
Auto
Test-Files {Eris}<Test>subsystem>Auto>
Aux-Files {Eris}<Test>subsystem>Auto-Aux>
Hand
Scripts {Eris}<Test>subsystem>Hand>
Aux-Files {Eris}<Test>subsystem>Hand-Aux>
File Naming
ÿÿï%.test
ÿA file of DO-TEST forms, suitable for running with DO-TEST-FILE or DO-ALL-TESTS. Within a directory, files are named x-y-z-w....test, with more general descriptions to the left, and more specific naming to the right. For example, there might be several tests of Lists: LIST-CREATION.TEST and LIST-MODIFICATION.TEST. It is poor form to include the words REGRESSION, TEST, or such like in the file name: Regression tests should be folded into the main test file, and all of these files are tests, so that's redundant.
ÿÿï%.u
ÿA script to be followed during hand testing. Within a directory, files are named x-y-z-w....u, with more general descriptions to the left, and more specific naming to the right. For example, the Exec might have several test files, e.g., Exec-PL.u, Exec-DIR.u, etc.
ÿÿï%.plan
ÿ A plan for testing a section of the system, a new product like PCE, etc.
ÿÿï%-m-d-y.logÿ
The results of running a test or series of tests.
.0.= $T@ Ô $0<@  $0<@ $0<.MODERNMODERN
MODERN
MODERN MODERN MODERN
MODERN(+N¦#1 6%!7'%gKRJ#$(+%+"%%G'



 

 "! ! K $# !# N*,0/ -/ T           
 L3~