How we test GalionToon
By Forge of Galion · September 25, 2026
Before a new version of GalionToon reaches your browser, it goes through more than two hundred automated checks. They are not a list someone skims through: they are tests that open the application in a real browser, do what a person would do and compare the result with what should come out. Here I explain what gets tested, which bugs were caught and why it is the foundation for everything else.
Why test before releasing
An editor works with what you create. A bug is not just an annoyance: it can cost you an afternoon of work or a file that no longer opens. On top of that, in a large application everything is connected. A change meant for phones can throw something off on tablets, and an improvement to masks can affect exporting. The only way to know nothing has broken is to check everything again, every time.
That is why the tests work like a user: they open a document, paint, crop, export, reopen the file and compare it pixel by pixel. If something does not match, the version does not go out.

What gets tested
- Selection and layers: 48 checks that select, move and transform layers, groups, masks and text, and verify that everything ends up where it should.
- Phone and tablet: the interface in portrait and landscape, the pinch and pan gestures, that every button is at least 44 pixels for a finger, the on-screen keyboard and the three screen modes.
- PSD: a document with text, rotations and masks is exported, reopened and compared with the original. The difference has to be zero.
- The site guides: each guide is generated and checked in its three languages: that all its screenshots exist, that the title fits on a phone and that its search engine data is valid.
- The font catalog: the 200 fonts are downloaded and applied, and every file was checked to have accents, ñ, ¿, ¡ and €.
Bugs caught before they reached anyone
Testing every step, while preparing the guides and with the automated checks, has brought real bugs to light before they reached anyone. A few examples:
- The gradient did not paint on the mask. With the mask selected, the gradient painted the photo instead of the mask. It came up while preparing the masks guide, and the guide waited until it was fixed.
- Shift did not draw a perfect circle. The tool’s help promised it, but dragging an ellipse with Shift produced an oval. Now it does what it says.
- Half-finished translations. Some windows mixed languages: with the application in English, Spanish text appeared. A test now goes through those windows in the three languages and fails if anything is left untranslated.
- A vector SVG that was not entirely vector. When exporting a logo, the shapes were stored as an image inside the file. It came up while preparing the vector guide; now a test opens the SVG in a vector editor and checks that it contains real paths.
Every bug that gets fixed leaves a new check behind, so that it does not come back.
A guide is not published if the app does not do what it promises
The same rule applies to the guides. Before writing one, the whole process is done in the application, from start to finish, and the screenshots come from there. If a step does not work the way the guide is going to describe it, the guide waits. That is what happened with the ones on animating with bones and converting a logo into a vector: they were postponed until Galion Rig could export the animation and the SVG stored real paths.
Facts that do not depend on the application are checked too, such as the sizes social networks ask for or the font licences. A claim that can be verified has to be true; if it is not, it is not published.
What it means for you
It means you can trust that what worked yesterday still works today, and that a guide will take you to the result it promises. It does not mean there are no bugs: no test covers everything. If you find one, tell me. It gets fixed and becomes one more check, and so the next version is a little more reliable than the last.
If you want to see the result of all this, try the guides that came out of those fixes: Layer masks, How to animate a character with bones and How to convert a logo into a vector.
More articles
- Bones for animation and real vectors: what’s new in GalionToonGalionToon now animates characters with bones and exports logos as editable vector SVG. Why I built them and what you can do with them.News · September 25, 2026
- Your files stay on your device: how GalionToon worksIn GalionToon your photos, PSDs and videos are not uploaded to any server: everything is processed in your browser. What that means exactly, what it costs and how to check it.How it works · September 25, 2026
- Seven mistakes that give away an amateur pixel art spriteUncontrolled palettes, blurred edges, pillow shading, black outlines… Seven common pixel art mistakes, with real before-and-after examples and how to fix them.Techniques · September 25, 2026