mirror of
https://github.com/aseprite/aseprite.git
synced 2024-12-29 00:23:48 +00:00
e865374805
Now the equivalent was "{tag}_{frame1}.png", but it looks like a regression reported here https://community.aseprite.org/t/17253 were it was possible to just specify the frame number as in "{tag}_1.png" |
||
---|---|---|
.. | ||
cli | ||
scripts | ||
sprites | ||
third_party | ||
LICENSE.txt | ||
README.md | ||
run-tests.sh |
Aseprite Tests
Test suite for Aseprite to avoid breaking backward compatibility.
This directory is cloned by the build.yml action to run several automated tests after Aseprite is compiled:
- Save/load file formats correctly. For this we have
.aseprite
,.png
,.gif
, etc. files sprites folder. - Test backward compatibility with Aseprite CLI options
- Future scripting API using scripts
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.