We often say that updates never break your site. That promise starts long before the update reaches you: it starts every time we change a single line of Cleitext.
A tireless inspector
Developers call it CI, continuous integration. Think of it as an inspector that never sleeps: each time we send a change, it takes a clean computer, builds Cleitext from scratch and runs more than a thousand checks. At the end it gives a traffic light: green, everything works; red, something broke, and it says exactly what.
What it checks
- The server, the admin and the plugins, on a real database, as on your site
- A person’s day: sign in, write a page, publish it, in Chrome, Firefox and Safari
- Accessibility of the admin, for people who use a screen reader or the keyboard
- Every library we use, for known security holes and for a license compatible with the GPL
- Speed and weight: the admin must stay light and pages fast, also with many entries
Green, or nothing ships
A new version is published only when every light is green. If a single test fails, we fix it first. It takes a few minutes more each time, and it is the reason a release does not surprise you.
And then, once more on your site
Our tests cannot know your site. So when you update, Cleitext tries the new version on the side first, with a backup: if it does not start, your site stays as it is. Two safety nets, one after the other.
Everything is public: the tests live next to the code on GitHub, and anyone can see the result of each run.
Comments
No comments yet.