Add a test template.
Add a load script test case in the template.

It is better to load the script to be tested inside a test case,
because this strategy works when the tests are loaded using
loadTestsFromFolder() (when the test scripts are loaded through
loadTestsFromFolder(), their run handler is not executed).
The alternative would be to load the script at compile time, but
that may be inconvenient.
Add a template test loader.
Add a runtime loader.

This script is just a curiosity, not that it has great practical
advantages over the other templates.
Clean scpt files in templates folder.
Remove Minitest.

MiniTest is an interesting experiment, but its
advantages are not overwhelming (especially
starting with AppleScript 2.3) and it has some
drawbacks (running all tests from a folder does
not produce a single report). Besides, keeping two
frameworks that provide mostly the same
functionality is a burden for the developer and
may be confusing for users.
Bump version number to 1.0.0.

ASUnit is essentially feature-complete, and the
last commit breaks compatibility.
Add an example folder with the HexString example.
Add MyScript.applescript.

This is a dummy script that makes the test template
run without errors.
Build scripts in examples and templates folders.
Do not load test loaders from test loaders.

When running all the tests in a given folder,
ignore files whose name starts with "TestLoader"
or "Test Loader".
Add compileSourceFiles() handler.

When running all the tests in a folder, compile
all the files in source form before adding all the
.scpt files. Compiling is necessary, because we
cannot use `run script` to load scripts in source
form (that would execute the run handler).
By doing so, we are able to run .applescript files
without manually compiling them.
Improve comment in test template.
Add an "asunit" task to build only ASUnit.

Use the "build" task to compile all the scripts.
Add a comment to the README about test loaders.