Cleanup

pawurb · Aug 27, 2024 · 15cd167 · 15cd167
1 parent 6d9bc51
commit 15cd167
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 12 deletions.
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
@@ -83,7 +83,7 @@ jobs:
           POSTGRES_PASSWORD: secret
           DATABASE_URL: postgresql://postgres:secret@localhost:5432/pg-locks-monitor-test
         run: |
-          bundle exec rspec spec/
+          bundle exec rake test_all
       - name: Run tests for PG 12
         env:
           PG_VERSION: 12
@@ -93,7 +93,7 @@ jobs:
           POSTGRES_PASSWORD: secret
           DATABASE_URL: postgresql://postgres:secret@localhost:5433/pg-locks-monitor-test
         run: |
-          bundle exec rspec spec/
+          bundle exec rake test_all
       - name: Run tests for PG 13
         env:
           PG_VERSION: 13
@@ -103,7 +103,7 @@ jobs:
           POSTGRES_PASSWORD: secret
           DATABASE_URL: postgresql://postgres:secret@localhost:5434/pg-locks-monitor-test
         run: |
-          bundle exec rspec spec/
+          bundle exec rake test_all
       - name: Run tests for PG 14
         env:
           PG_VERSION: 14
@@ -113,7 +113,7 @@ jobs:
           POSTGRES_PASSWORD: secret
           DATABASE_URL: postgresql://postgres:secret@localhost:5435/pg-locks-monitor-test
         run: |
-          bundle exec rspec spec/
+          bundle exec rake test_all
       - name: Run tests for PG 15
         env:
           PG_VERSION: 15
@@ -123,5 +123,5 @@ jobs:
           POSTGRES_PASSWORD: secret
           DATABASE_URL: postgresql://postgres:secret@localhost:5436/pg-locks-monitor-test
         run: |
-          bundle exec rspec spec/
+          bundle exec rake test_all
 
diff --git a/README.md b/README.md
@@ -49,7 +49,7 @@ end
 
 ## Testing the notification channels
 
-Before configuring a recurring invocation of the `snapshot!` method, it's recommended to first manually trigger the notification to test the configured channels.
+Before enabling a recurring invocation of the `snapshot!` method, it's recommended to first manually trigger the notification to test the configured channels.
 
 You can generate an _"artificial"_ blocking lock and observe it by running the following code in the Rails console:
 

diff --git a/spec/smoke_spec.rb b/spec/smoke_spec.rb