Test65

This is a simple program written to allow the testing of 65C02 code that I am writing for the Commander X 16 neo-retro computer.

Note: This program has recently undergone a lot of upgrades and is now ready to release as a Ruby gem.

To install, first install the cc65 compiler and ensure that it is available at the command line. You can test the required components with:

ca65 --version
ld65 --version
sim65 --version
set CC65_HOME

Then to install the gem, use:

$ gem install test65

test65 - Run tests of 65c02 assembler code.

Usage: test65 {options} {files}

Options:
  --debug,   -d    Show (really) detailed debug info. Not normally required.
  --help, -h, -?   Display this message and exit.
  --list,    -l    Generate list files for each test.
  --map,     -m    Generate map files for each test.
  --keep,    -k    Keep object and output files. Do not clean up.
  --path,    -p    Specify the path to the test files. (Only 1 allowed)
  --quiet,   -q    Hide messages. Used to keep the test65 tests clean.
  --verbose, -v    Display lots of useful progress info.
  --version        Display the program version and exit.

Files: An optional list of test files.

Notes:
- By default, test files are located in a folder called "t65" in the current
  folder or one of its parent folders.
- Wildcards are allowed for files but not the path.
- If no files are specified, then all files matching "t65*.a65" or "t65*.rb"
  in the test folder are tested.
- If files are specified, only the specified file(s) are tested.

The test65 utility finds test files in one of two ways:

1. The test files can be listed explicitly on the command line.
2. Test files, of the appropriate extension, located in the test folder, are "batch" run.

The tests are located in a test folder. This can be:

1. Explicitly named using the --path option. (See above)
2. Located in the t65 folder, either off of the current folder, or one of its parent folders.

Test files can be:

1. Assembly files with a suffix of ".a65".
2. Ruby script files with a suffix of ".rb".

Future versions may support alternate extension types for assembler (like ".asm" for example) and tests written in the "C" language with extensions of ".c65" and maybe ".c".

The test65 gem uses Ruby scripts to allow for cases not handled by the conventional defaults. The basic form of these scripts is:

# Minimum script to pass a test.

Test65.script do
  ca65 "min_pass.a65"
  ld65
  sim65
end

The order matters and is:

assembly and compiling then linking then simulation

If the order is wrong, there will be errors.

Code is assembled using the ca65 statement. It is supported by the ca65_inc_paths method. They are:

ca65_inc_paths <path>, <optional more paths>, <etc>, <etc>, <etc>
ca65 "source_file", "optional options"

Where ca65_inc_paths is used to tell the assembler where to find included files and ca65 does the work of converting the source file to an object file.

Code is linked using the ld65 statement. It is supported by the ld65_lib_paths and ld65_libraries. Here they are:

ld65_lib_paths "path to libraries", <etc>, <etc>, <etc>
ld65_libraries "library", <etc>, <etc>, <etc>
ld65 "optional options"

Where ld65_lib_paths tells the linker where to find library files and ld65_libraries specifies those libraries. After any ld65 method, no further ca65* methods are permitted. After ld65 no further ld65* methods are permitted either.

Finally, the simulation phase runs the actual tests. This is simply:

sim65 "optional options"

When this is done, no further test statements are permitted. However it is possible to perform multiple tests in one script file. Simply code multiple Test65.script { ... } blocks in the one Ruby script file. They will be run one after another, in order.

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

OR...

• Make a suggestion by raising an issue . All ideas and comments are welcome.

The gem is available as open source under the terms of the MIT License.

Everyone interacting in the test65project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.