From 6f404e77b60c7d55c2bd6fad46d5ea13a99650f0 Mon Sep 17 00:00:00 2001 From: David Cook Date: Mon, 4 Mar 2024 12:40:15 +1100 Subject: [PATCH] Remove outdated Capybara `have_no` recommendation (now enforced by rubocop in https://github.com/openfoodfoundation/openfoodnetwork/pull/12224) --- Code-Conventions.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/Code-Conventions.md b/Code-Conventions.md index 5cb3ddb..10a3744 100644 --- a/Code-Conventions.md +++ b/Code-Conventions.md @@ -33,9 +33,6 @@ When you have to insert an arbitrary Ruby string to a Javascript or Angular expr # Tests -### Prefer `to have_not` as a feature matcher style (instead of `to_not have`) -Reference: Capybara finders section of [this blog post](https://blog.codeship.com/faster-rails-tests/) for more details. - ### Prefer plain text over method calls in expected values For example, when asserting text that is translatable, use plain text instead of the `I18n.t` call.