Ruby Testing
What a test actually asserts, and where that claim is weaker than it looks. Argument order and failure messages, the three kinds of equality, exceptions, isolation between examples, and the difference between a failure and an error.
Who it is for
Tests the code they wrote, not the code they meant.
The behaviour people get wrong after they are already productive in the language.
You will get the most out of it if you have written Ruby recently enough to read it without effort, and have been surprised by it at least once. If you are picking the language up for the first time, start with Ruby Essentials and come back to this one.
How long it takes
90 graded questions at roughly 45 seconds each is about 68 minutes of answering in total.
At the default five questions a day, and because the session mixes in your other courses, expect around 18 days — call it 3 weeks — to see everything once, plus a few weeks of thinning reviews after that before it is all mastered.
A question is mastered on the third correct answer, once the gap between reviews has grown past a week — so a course cannot be finished in a weekend however long you sit with it.
Question mix
- 60 multiple choice
- 10 concept cards
- 10 predict the output
- 10 put it in order
- 10 matching questions
Syllabus
What you will be asked about
-
01
What a Test Asserts
Say what a given assertion actually pins down, and what it leaves free.
-
02
Expected First, Actual Second
Put expected and actual in the order the failure message assumes.
-
03
==, eql? and equal?
Choose between ==, eql? and equal? when writing an assertion.
-
04
Testing That Code Raises
Assert that code raises, and assert it raises the thing you meant.
-
05
setup, the Test, teardown
Predict the order setup, the test body and teardown run in, and what each may assume.
-
06
Isolation and Shared State
Spot the state one test leaves behind for the next one to find.
-
07
Stubs and Dependency Injection
Choose between replacing a method and passing the collaborator in.
-
08
What a Mock Verifies
Say what a mock proves that a stub cannot.
-
09
Floats in Assertions
Assert on a floating point result without writing a test that cannot pass.
-
10
Failures, Errors and Private Methods
Tell a failed claim from a broken test, and decide what to do about a private method.
8 more topics, and all 90 questions
Ruby Testing is a Pro course. One subscription opens it and every other course in the catalogue, including the ones still being written.
A question from this course
What a Test Asserts
What does this print?
vals = [0, "", [], nil, false]
puts vals.map { |v| v ? "T" : "F" }.joinShow the answer
A TTTFF
You may have expected 0 and "" to be falsy because they are in C, Python and JavaScript. In Ruby only nil and false are falsy, so assert 0 and assert [] both pass. That is why assert cart.size is a much weaker claim than it looks.
The rest of the track
Ruby at every depth
Ruby Essentials
The behaviour underneath the friendly syntax. Only nil and false are falsy, symbols are not strings, string literals are mutable, and a method returns its last expression whether or not you meant it to.
Ruby Core
Where Ruby trips people who use it daily. Blocks against procs against lambdas, the ancestor chain and method lookup, the three kinds of equality, and what happens when two names point at the same object.
Ruby Data & Collections
Array, Hash, Set and Enumerable in earnest. Bang methods that return nil, Hash defaults that share one object between every key, fetch against [], grouping and tally, and lazy enumerators that are not always cheaper.
Ruby Errors & Edge Cases
Exceptions and their edges. Rescue ordering, StandardError against Exception, what an ensure does to a return value, retry, and the difference between catch/throw and raising at all.
Ruby Standard Library
The library people reimplement by hand: Struct and Data, Set, the Comparable and Enumerable mixins, Forwardable, JSON, Digest and BigDecimal. Ten places where a built-in already does the job, and one behaviour in each that is not what you assumed.
Ruby Idioms & Pitfalls
The Ruby people write out of habit that is wrong or merely un-Ruby: for loops that leak their variable, and versus &&, unless with an else, ||= on a false value, map followed by compact, and rescuing Exception. Ten habits, and the behaviour that punishes each one.
Ruby Advanced
The metaprogramming that still catches experienced Rubyists: singleton classes, method_missing, refinements, prepend, and the two searches behind constant lookup. Every snippet is one you could be handed in a code review.
Ruby Performance
What actually costs in MRI: object allocation, frozen and deduplicated strings, symbol keys, array and string growth, lazy enumerators, and the generational collector. Every claim is one you can measure with GC.stat rather than guess at.
Ruby Interview Questions
The Ruby questions interviewers actually ask, and the answers that need a reason attached. Proc and lambda return semantics, the ancestor chain, mixins, duck typing, shared references, symbols, method_missing, memoisation and Enumerable built by hand.
Start Ruby Testing
in tomorrow’s session.
Enrol and this course joins your daily five, mixed in with everything else you are studying — 90 questions spread over about 18 days rather than dropped on you at once.
Browse the catalogue