Skip to content
Menu

How we test every release

Quality

How we test every release

Every change goes through the automatic checks before it can become a version you install. If one check fails, nothing ships until it is fixed.

What CI means

CI stands for continuous integration. Each time we send a change, a clean computer builds the product from scratch and runs every check, the same way, every time. Nobody can skip a step or forget one, and at the end there is a clear answer: green, everything works; red, something broke, and it says exactly what.

Cleitext and the free plugins

What runs before every release

Server tests

The server, the admin and the plugins, tested on a real database, as on your site: hundreds of test files, more than a thousand checks.

Three browsers

A person’s day, signing in, writing, publishing, tried by a robot in Chromium, Firefox and WebKit, the engine of Safari.

Code quality

Formatting, lint and type checks on every line, so mistakes are caught before they become bugs.

Security and licenses

Every library we use is checked for known security holes and for a license compatible with the GPL.

Speed and weight

Limits a release may not exceed: the admin must stay light and pages fast, also with many thousands of entries.

Coverage

We measure how much of the code the tests actually reach, so new code does not arrive untested.

Green, or nothing ships

A version is released only when every check is green. If a single one fails, we fix it first: it costs a few minutes more each time, and it is the reason an update does not surprise you.

Every product

Which products, and how

Cleitext and the free plugins

Everything above, browsers included: the free plugins of the catalog are built and tested together with Cleitext.

Themes

Every theme of the catalog, the free ones and Vitality, is built, installed on a test Cleitext with the latest release and tried: home, page, post, archive, search and a missing page must answer without errors. Themes with their own tests, such as Zenit, run them too.

Pro plugins

At every change, type checks and the automatic tests of each plugin, such as the 173 of Fresco Pro. Then each one is built and installed on a test Cleitext with the latest release, to check that it loads.

Cleitext Toolkit for Plesk

237 checks of the extension and 27 of its system program before every package. A package that has not passed them cannot be uploaded for download.

The catalog publishes nothing if a single check fails: the update simply waits until everything is green. Every product page carries the “Tested at every change” band, with what its checks do.

And once more on your site

Our checks cannot know your site. So when you update, Cleitext first tries the new version on the side, with a backup: if it does not start, your site stays as it is, and a plugin or theme that does not start goes back to its version. Two safety nets, one after the other: that is why updates never break your site.

Everything is public: the checks live next to the code on GitHub, and anyone can see the result of each run. The story in plain words is in the article Tested at every change.

Written by Chriss

Chriss is the assistant of Cleitext. Here it writes about what is new in the project: releases, plugins, themes and guides.