Testing is the only way to ensure that your code works.

Enter your email.

Oops. There's something wrong with your email.

While manual testing is usually good enough for small projects, it quickly becomes time-consuming and annoying. The bigger your application grows, the more things you need to re-test every time something changes.

Regressions are coming.

Manually testing may seem like it's enough. Until you break something and deploy before realizing your mistake - that's called a regression, and it's bad. Very bad.

You don't want to be the dev who introduces regressions, right?

What if there was a way to ensure that your code is working as expected today, tomorrow and every day after that?

Well, there is.

It's called automated testing and it's easier than you think, especially with Ruby and all its cool frameworks.

Learning how to write automated tests for your Rails applications will allow you to save time and money, sleep better at night, reduce your stress level and increase the quality of your applications - potentially leading to a better pay and/or more clients.

Automation is more and more part of our lives - so say NO to manual testing and YES to automated testing!

Now let me tell you a story...

A long time ago in a galaxy far, far away, I used to think my code was good enough on its own - I didn’t need to write, or even think about automated tests - they were a waste of my time.

Boy, was I wrong!

This bad attitude towards writing automated tests led to memorable (read: painful) periods where I had to re-test everything by hand, spending hours clicking around… talk about a waste of time. And let’s not forget the epic bug I pushed to production which prevented users from finishing the checkout process (which is arguably the most important part).

Today, I feel like I was a bit irresponsible. I had one job - to develop features that work with the least amount of bugs. Well, I was playing with fire and I got burned.

Luckily, I was later able to integrate a great team of engineers who taught me how important automated tests were. They showed me not only how to write them, but also the best (and worst) practices related to automated testing.

A few years later, here I am, loving automated testing and preaching it to everyone I can. That’s why I decided to create something to take you from where I was to where I am today ;)

Before I get into the specifics...

… let’s talk about some stuff you already know.

You know Basecamp, right? Made by Basecamp (formerly known as 37Signals), built with Ruby on Rails. What about Thoughtbot? They design and develop solutions for their clients and share web development tutorials/tips (which are often related to Rails). Now, think about one famous developer that you admire. Maybe he is working on a big open-source project that you’re using, or he works for a successful company that you admire.

Well, you know what all these people and companies have in common? They all create very high-quality applications and tools - and to ensure this quality, they write automated tests.

Can you imagine if the Ruby on Rails framework didn’t have any tests? You wouldn’t be able to rely on it working as expected to build your own stuff on top. Scary.

Writing automated tests will not only help you create better products for yourself or your clients, but will also give you the tools to become a better developer. Writing tests will make your coding mistakes apparent, allow you (or someone else) to refactor without fear and give you the confidence you need to deploy an application to thousands (or millions) of people.

Now let’s go back to that “something” I was talking about.

That "something" is...

Rails 5 Testing: Why, Where and How

A video course focused on automated testing with Rails 5, RSpec and a few other tools.

What is it?

Rails 5 Testing: Why, Where and How is a video course that will teach you pretty much everything you need to know to get started writing automated tests in your Rails applications with RSpec.

You will also learn about different testing styles to find the one that suits you. Once you’ve completed the course, you will have a good understanding of Test-Driven Development (TDD), Behavior-Driven Development (BDD), Tests After and Tests First!

What if I think automated tests are a waste of time?

I believe it’s important to keep an open mind when working as a developer. The benefits of automated tests go beyond yourself, and help your team and your entire company. Take a leap of faith. Give it a try and you might end up loving it. I know, because I’m a convert myself.

What if I want to write tests, but my team/boss thinks it’s a waste of time?

While having a company and a team committed to testing is the best way to create complete test suites for your Rails applications, I understand that it’s not always possible.

Why not?

Well, I’ve seen places where testing is frowned upon and seen as a waste of time. In other places, developers simply don’t have time to write tests because they are pushed to add more features ASAP (even if the features end up half-broken…).

But changing minds is hard. You need to do it slowly…

That’s why I also explain how to get started writing tests in an environment hostile to tests, in a discreet and minimal way. Spending just a tiny bit of time writing a few tests can have a tremendous effect on your projects. The better you get, the faster you will be able to write them - the quality of your applications will go up and your team and/or boss might finally start to see the benefits.

But wait, what’s in the course exactly?

Oh right! Well, scroll down to find out what’s in the course exactly.

The Videos

Coming Soon.


Enter your email.

Oops. There's something wrong with your email.

No Spam. Unsubscribe Anytime.