Return to readme.txt CVS log

Up to [HATARI the Atari ST Emulator] / hatari / tests / tosboot

Annotation of hatari/tests/tosboot/readme.txt, revision 1.1.1.1

1.1       root        1: 
                      2: Usage
                      3: -----
                      4: 
                      5: If you want to test Hatari version that isn't in your PATH,
                      6: you need to give PATH for the Hatari binary you want to test,
                      7: like this:
                      8:        PATH=../../build/src:$PATH ./tos-tester.py <TOS images>
                      9: 
                     10: To view the produced screenshots, either use ImageMagick:
                     11:        display *.png
                     12: 
                     13: Or use the script that creates a HTML page with them and opens
                     14: browser to view it.
                     15: 
                     16: 
                     17: What TOS tester tests
                     18: ---------------------
                     19: 
                     20: These are the HW configurations combinations that TOS tester currently
                     21: supports:
                     22: 
                     23: * ST, STE, TT, Falcon machine types
                     24: 
                     25:   EmuTOS 512k is tested for all the machine types, EmuTOS 192/256k and
                     26:   TOS v2.x with all except Falcon, rest of TOSes are tested only with
                     27:   a single machine type.
                     28: 
                     29: * TV, VGA, RGB and monochrome monitors and 1 & 4 plane VDI modes
                     30: 
                     31:   ST:     tv,  mono, vdi-1, vdi-4
                     32:   STE:    rgb, mono, vdi-1, vdi-4
                     33:   TT:     vga, mono, vdi-1, vdi-4
                     34:   Falcon: rgb, mono, vga
                     35: 
                     36: * Different amounts of memory
                     37: 
                     38:   ST:   0.5 &  2 MB
                     39:   STE:    1 &  4 MB
                     40:   TT:     2 & 10 MB
                     41:   Falcon: 4 & 14 MB
                     42: 
                     43: * With and without GEMDOS harddisk directory emulation
                     44: 
                     45: 
                     46: What to test
                     47: ------------
                     48: 
                     49: For each Hatari release it would be good to test e.g. the following
                     50: TOS versions:
                     51:   v1.00 de, v1.02 de, v1.04 de, v1.04 us, v1.62 de, v1.62 us,
                     52:   v2.06 de, v3.06 us, v4.04, etos192k, etos512k[1]
                     53: 
                     54: [1] Just the latest release of EmuTOS.
                     55: 
                     56: This should give good enough coverage of all the possible bootup
                     57: issues.
                     58: 
                     59: 
                     60: TODO
                     61: ----
                     62: 
                     63: * Don't use timeout and screenshot, but something more robust:
                     64: 
                     65: With GEMDOS HD emulation, auto-run some Atari program that writes to
                     66: a predefined file, which in actuality is a FIFO that the tos-tester
                     67: listens on.  If there's no write within some long timeout, the tester
                     68: would conclude boot to have failed.
                     69: 
                     70: Otherwise, redirect MIDI or RS232 to a file and boot a floppy disk
                     71: with an autostarted program that writes something to the corresponding
                     72: interface.
                     73: 
                     74: (Both need to be tested as GEMDOS HD emulation could influence the
                     75: behaviour of the emulation quite a bit since it uses a cartridge and
                     76: trap-bending mechanisms internally.)
                     77: 
                     78: 
                     79: * Command line options to specify what exact tests are run (memory,
                     80: graphics, arbitrary Hatari option) and to specify full of range
                     81: additional values for the tests:
                     82:        --test mem,gfx --graphics vga,vdi-1,vdi-2 --memory 0,2,8 \
                     83:        --test-bool "--fast-boot" --test-bool "--compatible"

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.