mirror of https://github.com/aseprite/aseprite.git synced 2024-10-03 05:22:23 +00:00

History

Gaspar Capello c8f018f2f1 Fix exporting a Sprite Sheet with Group name has different functionality between CLI and Scripting (fix #4456 ) (#4475 ) Before this fix, the lua command: app.command.ExportSpriteSheet could not process a layer within a group when the layer name was expressed using the layer hierarchy path, for example: layer = "Group1/Layer1"		2024-09-03 20:20:36 -03:00
..
cli	Add --play-subtags CLI test	2024-05-28 15:00:22 -03:00
scripts	Fix exporting a Sprite Sheet with Group name has different functionality between CLI and Scripting (fix #4456 ) (#4475 )	2024-09-03 20:20:36 -03:00
sprites	Add --play-subtags CLI test	2024-05-28 15:00:22 -03:00
LICENSE.txt	[lua] Add short field names (fix #3815 , fix #3816 )	2023-04-19 13:48:15 -03:00
README.md	Fix instructions/paths for CLI tests	2022-10-25 15:57:31 -03:00
run-tests.sh	Merge remote-tracking branch 'tests/main'	2022-10-25 15:30:38 -03:00

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.