Sha256: 358824f0b064ac126b9563e7e031528b835421c773adce4ae0f4c297a0d3dc5f
Contents?: true
Size: 965 Bytes
Versions: 11
Compression:
Stored size: 965 Bytes
Contents
Feature: checks for vulnerable gems In order to find vulnerable gems As a ruby developer I want to run warder with --bundle-audit option Scenario: run warder with enabled bundle audit option Given I have valid_rails_app project in directory And I am on project directory When I run `warder --bundle-audit` Then warder detects gem freshness issues Then the exit status should be 0 Scenario: run warder with enabled bundle audit option on invalid file Given I have invalid_rails_app project in directory And I am on project directory When I run `warder --bundle-audit` Then warder detects gem freshness issues Then the exit status should be 1 Scenario: run warder with disabled bundle audit option on invalid file Given I have invalid_rails_app project in directory And I am on project directory When I run `warder --no-bundle-audit` Then warder does nothing Then the exit status should be 0
Version data entries
11 entries across 11 versions & 1 rubygems