Last week, we shared the first episode Semaphore Uncut, in which our co-founder Darko Fabijan showed you around Semaphore 2.0. In this week’s episode, you’ll learn how to automatically promote continuous delivery pipelines in Semaphore 2.0.
We’re excited to let you know that this week we started making Semaphore Uncut, a weekly live video stream in which we will talk about Semaphore 2.0, our new continuous integration and delivery (CI/CD) product, as well as other topics relevant to Semaphore users with everyone interested to join us live.
Adoption of serverless technology is surely growing, with emerging product companies who built on top of it. One of them is CloudZero, a Semaphore customer, who recently wrote a detailed article about their experience in achieving continuous delivery for their all-serverless system.
Semaphore 2.0 closed beta is now available. Make sure to get on the list for an early invite. With powerful, fully customizable CI/CD pipelines, Semaphore 2.0 makes it easier than ever to deliver great products at high velocity. It’s designed to accelerate the way engineering teams of all sizes build, test and deploy their projects. […]
Introduction In this tutorial, we’ll be looking at one of the main use cases for test doubles in Elixir: aiding in the interaction between domain logic and impure components that exist over the boundaries of an application. Tests relying on such components are usually brittle, and need to reach out to external resources whose state […]
In April, we officially released Rails Testing Handbook, a free ebook in which our engineers shared how to write tests and practice BDD to develop sustainable Rails applications. The handbook teaches you all you need to know about the BDD approach of analyzing, testing, coding, and designing a system in one short feedback loop. BDD […]
Today we’re happy to announce general availability of the Docker Light platform. Based on Ubuntu 16.04 LTS, the environment provides one physical CPU (2 vCPUs), 4GB of RAM and 10GB of disk space.
At Semaphore, for years we’ve been happy to support open source projects with a free continuous integration service. Today we’re increasing the free CI/CD capacity on all open source organizations from 2 to 4 Boxes.
Earlier, we launched Semaphore Boosters, a feature that allows you to automate parallelizing your RSpec and Cucumber tests in a few clicks. The feature has helped many teams to reduce their Rails CI build times by as much as 2 hours in some cases. Initially, the feature was available only to some users. It has […]
This post is adapted from Rails Testing Handbook, a free ebook on building sustainable Rails apps with BDD. In this tutorial, we will guide you through the process of generating a new Rails 5 application, with all the necessary tools to set up a behavior-driven development (BDD) flow. We will set up 5 tools that […]
Introduction This tutorial is the last in a series of tutorials concerning the container orchestration tool, Docker Swarm. In this series, we’ve already seen how to establish a Swarm cluster, schedule services to the cluster’s nodes, make those services consumable from within and outside the cluster, and update and rollback services in-flight. We’ve mainly focused […]
This is the second post in the series about antipatterns in testing Rails applications. See part 1 for thoughts related to fixtures and factories. Creating records when building would also work It is common sense to say that with plain ActiveRecord or a factory library you can both create and only instantiate new records. However, […]
In the upcoming series of posts, we’ll explore some common antipatterns in writing tests for Rails applications. The presented opinions come from our experience in building web applications with Rails (we’ve been doing it since 2007) and is biased towards using RSpec and Cucumber. Developers working with other technologies will probably benefit from reading as […]
This tutorial has been updated by Thiago Araújo Silva on 20 April 2018. Introduction In test-driven development, data is one of the requirements for a successful and thorough test. In order to be able to test all use cases of a given method, object or feature, you need to be able to define multiple sets […]
