Cheatsheet recap

One line per idea, in order. The pause-for-questions slide.

Idea	Remember
Why test at all?	tests are the confidence to change code, not a chore on top of it.
Your first test	a test is a plain function with #[test] on top, living in a cfg(test) module.
Pick the right assertion	prefer assert_eq!, its failure message hands you the two values for free.
Test the panic	#[should_panic(expected = ...)] tests that the unhappy path fails the right way.
Tests can return errors	return Result from a test so ? can short-circuit a failure for you.
Two homes for tests	unit tests see everything, integration tests see only your api.
Run the slice you need	run the slice you need, not the whole suite every time.
Read the result	red shows the exact left and right values, so you debug before you open the code.

All slides