https://github.com/tdooner/rspec-intro-talk
Materials for an intro talk about rspec/testing
https://github.com/tdooner/rspec-intro-talk
Last synced: 3 months ago
JSON representation
Materials for an intro talk about rspec/testing
- Host: GitHub
- URL: https://github.com/tdooner/rspec-intro-talk
- Owner: tdooner
- Created: 2022-09-27T22:46:30.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2022-09-27T23:06:11.000Z (over 2 years ago)
- Last Synced: 2025-01-15T00:29:24.361Z (5 months ago)
- Size: 1.95 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# RSpec Intro Talk
by Tom Dooner
10-11-2022
# Overview of this "talk"
Here's how this is meant to go.
1. Read the remainder of the README.md as an intro
2. Open this repo in github.dev.
3. We'll go through the example directories together.
# "Testing" - The what and why
Testing allows us to verify that our code behaves as expected, now and in the future.
This is important because nobody can keep a full mental picture of how a codebase should behave.
What are some different types of tests?
You'll hear these general terms that describe the "surface area" that a test covers:
* __Unit Tests__: Tests of individual methods (small surface area, isolated, "units")
* __Integration Tests__: Tests of an integrated system. (large surface area, entangled)
Rails and RSpec have a lot of different "types" of test, dependending on what you're trying to test. Here are some that we use (in order of increasing surface area):
* __Model Specs__: Tests of methods on a given Model.
* __Controller Specs__: Tests of request processing logic in a Controller.
* __System (or Feature) Specs__: Integration tests of a full page render. Sometimes uses a simulated browser to even test JavaScript.
Almost all Rails framework entities (Views, Routes, etc.) can be tested, but teams vary on whether we find those valuable.