A deployment pipeline lays out the whole process that your code needs to go through from your repository to production. It breaks the build into several parts (e.g. build, test and deploy) and all the associated steps that need to be taken. In this post I'm going to talk through the steps of a simple deployment pipeline as used in the Tealeaf Academy course.
In my previous post about using Sidekiq for sending emails as a background job I went through the process of setting it up on a local server but in this post I'm going to talk about getting it working with my production server on Heroku.
I'm going to walk you through the steps of how to send emails as a background job in your application using Sidekiq and also how to test this.
In todays post I want to talk sending automated emails in an example scenario for when a someone signs up as a user for your application.
In my last post on Dynamic CSS Elements for feature tests in Capybara I discussed techniques to get a handle on the attribute for an object in a list for example. The main disadvantage with this however is that it in many cases you have to alter your view code in order to run your feature tests which I don't really like the idea of.
For my third week of course three in the Tealeaf Academy course I have been learning how to implement feature tests using Capybara. One of the feature tests involved checking that a user could successfully change the order of a list of videos. The list had several columns, one of which had text fields to allow the user to input numbers to change the list order.
Before I discuss Capybara I think it will help if I discuss to discuss about the type of testing you can use to ensure that a feature of you site works from beginning to end.
Feature specs are used when you want to test things from the user browser and integrate the different Rails components such as models, controllers, views, helpers, etc to ensure that a feature is properly implemented
Request specs are used when you want to go across multiple requests and responses to ensure that things execute in a sequence.
In this post I want to demonstrate how I can code up my own custom form builder that will help to cut down on the amount of repetition across my application and also make my forms look a lot cleaner.
This is a very short post but I just wanted to make a quick note on rake commnads that I found out this week. Here's a few things I found useful:
rake -T to get the most common rake commands
rake -T -A to get all of the rake tasks
rake -T -A |...
Red-green-refactor is an important concept in TDD when you are using tests to drive your code and I'll use an example to demonstrate how this works. First I start off with a series of descriptions about what I want my code to do. As an example, I have a todo list that has a name and description and I want to write a method that checks if my object only has a name defined. So my initial test setup would be:
describe :name_only do
it "returns true if the description is nil"
it "returns true if the description is an empty string"
it returns false if the description is a non empty string"
end