Testing

The testing procedure outlined below while not very formal or thorough will help ensure some level of uniformity when testing and will also test the main features of xAce. It is intended that this procedure should be followed before each release of xAce.

Operating Systems

When testing xAce it is important to know the following things about the set up that you tested it on:

• The name of the operating system (GNU/Linux, FreeBSD, etc)
• The operating system distribution and version: (FreeBSD 8.01, Ubuntu 10.04, etc)
• The processor architecture (i386, x64, ARM, etc)
• The bpp (Bits Per Pixel) of the display (8,16,32,etc)

Jupiter Ace Software Compatibility

The programs currently known to work under xAce should be tested to ensure that they stil work at each testing point. These are listed on the Compatibility page of the Wiki.

Loading/Saving .tap Files

Dictionary Loading/Saving

1. Run xAce
2. Enter the following definition: star 42 emit ;
3. Enter save star
4. Quite out of xAce
5. Check that there is a file called star.tap in the current directory
6. Run xAce
7. Enter load star
8. Enter vlist
9. Check that the last two entries in the dictionary are star followed by forth
10. Enter star
11. Check that a * is output

Binary Loading/Saving

1. Run xAce
2. Enter the following definition: 8896 32 bsave tstbsave : test ." Working" ;
3. Quite out of xAce
4. Check that there is a file called tstbsave.tap in the current directory
5. Run xAce
6. Enter 8928 0 bload tstbsave
7. Enter vlist
8. Check that the last two entries in the dictionary are test followed by forth
9. Enter test
10. Check that a Working is output