From 4c17989711a76866214f71f645fdf8fe785c15ad Mon Sep 17 00:00:00 2001 From: mms Date: Tue, 5 Dec 2023 11:57:10 +0100 Subject: chore: extract old blog posts to section --- content/2023/rspec-options.md | 21 --------------------- 1 file changed, 21 deletions(-) delete mode 100644 content/2023/rspec-options.md (limited to 'content/2023/rspec-options.md') diff --git a/content/2023/rspec-options.md b/content/2023/rspec-options.md deleted file mode 100644 index fceee63d..00000000 --- a/content/2023/rspec-options.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -title: "Specimen control with RSpec's options" -category: engineering -abstract: RSpec got some cool options for setting what we will test -date: 2023-03-31T22:54:50+02:00 -year: 2023 -draft: false -tags: -- Ruby -- RSpec -- Engineering ---- -Did you know that you can control which tests are run using RSpec's runner options? There are a few options I use every day: - -- `--seed=` - random order of tests is done by generating a random number, a seed. You can force given order by passing in [seed value](https://rubydoc.info/github/rspec/rspec-core/RSpec%2FCore%2FConfiguration:seed). Great for repeating order from CI! -- `--only-failures` - only tests that failed in the previous run will be run. -- `--fail-fast` - stop run after first encountering failure. - -Today I also learned about `--bisect`, which, in a flaky suite, will find the minimal set of tests that will fail the suite. Magic! - -You can find a lot more of such options on [Github](https://github.com/rspec/rspec-core/tree/main/features/command_line). -- cgit v1.2.3