2022-10-25 18:24:58 +00:00
|
|
|
# Aseprite Tests
|
|
|
|
|
|
|
|
Test suite for [Aseprite](https://github.com/aseprite/aseprite)
|
|
|
|
to avoid breaking backward compatibility.
|
|
|
|
|
2022-10-25 18:57:31 +00:00
|
|
|
This directory is cloned by the
|
|
|
|
[build.yml](https://github.com/aseprite/aseprite/blob/main/.github/workflows/build.yml)
|
|
|
|
action to run several automated tests after Aseprite is compiled:
|
2022-10-25 18:24:58 +00:00
|
|
|
|
|
|
|
* Save/load file formats correctly. For this we have `.aseprite`, `.png`,
|
2022-10-25 18:57:31 +00:00
|
|
|
`.gif`, etc. files [sprites](https://github.com/aseprite/aseprite/tree/main/tests/sprites)
|
2022-10-25 18:24:58 +00:00
|
|
|
folder.
|
|
|
|
* Test backward compatibility with [Aseprite CLI](https://www.aseprite.org/docs/cli/) options
|
2022-10-25 18:57:31 +00:00
|
|
|
* Future [scripting API](https://github.com/aseprite/api) using [scripts](https://github.com/aseprite/aseprite/tree/main/tests/scripts)
|
2022-10-25 18:24:58 +00:00
|
|
|
|
|
|
|
## How to run tests?
|
|
|
|
|
|
|
|
You have to set the `ASEPRITE` environment variable pointing to the
|
|
|
|
Aseprite executable and then run `run-tests.sh` from Bash:
|
|
|
|
|
|
|
|
export ASEPRITE=$HOME/your-aseprite-build/bin/aseprite
|
|
|
|
cd tests
|
|
|
|
bash run-tests.sh
|
|
|
|
|
|
|
|
You can filter some tests with a regex giving a parameter to
|
|
|
|
`run-tests.sh`, for example:
|
|
|
|
|
|
|
|
run-tests.sh color
|
|
|
|
|
|
|
|
Should run all tests which have the `color` word in their name.
|