Sha256: 55548ce327390d12607452fab96918bad9501a70a42bb05dbb9a76f1a4c326fe

Contents?: true

Size: 833 Bytes

Versions: 5

Compression:

Stored size: 833 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 gemfile in 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 gemfile in 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 gemfile in directory
    When I run `warder --no-bundle-audit`
    Then warder does nothing
    Then the exit status should be 0

Version data entries

5 entries across 5 versions & 1 rubygems

Version Path
warder-0.1.6 features/checks_for_vulnerable_gems.feature
warder-0.1.5 features/checks_for_vulnerable_gems.feature
warder-0.1.4 features/checks_for_vulnerable_gems.feature
warder-0.1.3 features/checks_for_vulnerable_gems.feature
warder-0.1.2 features/checks_for_vulnerable_gems.feature