Blog /Technology

We do a lot of Drupal development. We also do a lot of automated testing. This is why we decided to complement the standard functionality of Codeception with some new modules dedicated to Drupal. This helps us a lot in our daily work. As in our previous article, all examples listed below will be based on a project based on docker-console, which is why we encourage everybody to read the previous articles first if you didn’t do so yet.

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. In this article, we would like to introduce you to the world of automatic tests using Codeception, based on this kind of a project.

People who follow our blog already know that we’re using Docker at Droptica.

If you are a Drupal developer, it is almost certain you have heard of drush. Drush is a commandline utility which allows you to interact with drupal, well - from command line. Every Drupal agency or any one worth his salt who does drupal development, uses drush because it masively speeds up drupal development, saving time and money.  Drush comes with many built in commands, but you can also add your own.

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.

Content creation using the Paragraphs module is a completely different approach compared to the "standard" content creation in Drupal. In short: we prepare the components (paragraph type) and then, during the creation of an entry, we select any of the available components.  The components can be simple elements containing text, contents with columns or such complex elements as sliders, videos or photo galleries.

It is obviously necessary to look for and take advantage of tools which can be used when delivering Drupal development services. It's time for another dose of information about our work at the Droptica company. Today we'll cover file versioning and application testing. Subversion Initial projects implemented with Drupal (still as OPENBIT) used the Subversion system (also known as SVN, project website) for file versioning.

Everyone who has ever worked in IT has surely stumbled upon communication issues between programmers and testers, or in other cases. Talking to programmers, you can hear many anecdotes regarding bug reports and feedback they have received. Working as a tester in a drupal agency, I see this issue from the other side, but I understand the developement team. When returning a task from tests, I often find myself wanting to write just: “It doesn’t work!”.

Over the course of recent years, websites have undergone a significant change. Many new services and social media websites have been created. Mobile applications now play a very significant role on the internet, and various on-line services exchanging data is nothing out of the ordinary anymore.

Time has already passed since the premiere of Drupal 8. New projects and modules are released all the time, and there is an ever-increasing number of projects compatible with version 8.x at drupal.org. Unfortunately, these versions are often still unstable and filled with various bugs. As of today, the number of additional modules available for Drupal 8 is around 2,250, compared to 12,400 Drupal 7 modules.