In this course, we will be testing a simple command line card game using RSpec. We'll cover the core three libraries: the first module covers the core syntax and command line runner core, the second the expectation library for expressing rich assertions about your code, and the third covers mocks, a powerful tool for specifying collaborations between objects and getting useful design feedback. The final module places RSpec in the wider Ruby ecosystem, looking at the major RSpec versions and common patterns you'll encounter in the wild. In addition to covering the technical aspects of using RSpec, we'll also cover best practices for using them so you get the most out of your test suite: different types of tests, what kinds of things to test, when different styles are appropriate. This is applied in numerous worked examples.
Hi everyone, my name is Xavier Shay, and welcome to my course, Testing Ruby Applications with RSpec. I'm on the core team for RSpec, the most popular Ruby testing library.
RSpec was released in 2005 and has since matured into a fully-featured and stable open source framework.
In this course, we'll be building up a test suite for a simple command line card game.
To do so, we'll be using the three main RSpec components. First, the core library, which contains RSpec's syntax and the command line runner. It's all you really need to get started.
Second, the expectations library will allow us to better express properties of our code rather than writing complicated checks ourselves. And thirdly, the mocks library, which allows us to easily create fakes for testing collaboration between objects and to get architecture design feedback on our code.
We'll go through the when, why, and how of using each of them, covering testing best practices along the way.
Before beginning this course, you should be familiar with the basics of the Ruby language.
I hope you'll join me on this journey to learn RSpec with the Testing Ruby Applications with RSpec course at Pluralsight.