Has it ever happened to you that when you were looking on a website, you weren’t sure whether a font you used was 12 pt or 13 pt? Or maybe you kept looking at an image, wondering whether it had been moved slightly to the left before? If the layout is a priority on your website, maybe it’s time to think about automating the testing of this aspect of your project. VisualCeption is a noteworthy solution for exactly this use case.
Taking into consideration the fact that most of our products are based on Drupal, the tests should also naturally work best with such projects. This is why we decided to complement the standard functionality of Codeception with some new modules dedicated for Drupal.
If you read our previous posts, you already know very well how to start a project in the docker-console. If you haven’t done it yet, you should start with this article, because for the purpose of this article we assume that your project in the docker-console is already up and running, therefore all commands executed below will refer to it.
When creating websites, you probably sometimes saw how your page changes its appearance on different browsers, not to mention a variety of devices. Depending on how many different configurations we will want to check, the amount of time spent on testing them will grow rapidly and the enthusiasm will probably decrease at a similar rate with repeating the same action on another device.
Everyone who has ever worked in IT has surely stumbled upon communication issues between programmers and testers, or in other cases, another person whose role was to check whether the task was completed correctly. Speaking with coders, you can hear many anecdotes regarding bug reports and feedback they have received. When returning a task, I often find myself wanting to write just: “It doesn’t work!” However, situations in which nothing actually works are pretty rare.