Sha256: 2cb4db94928509853505013c5e077fed85ea63bf3ecc4c873e9654ccc5ca8502
Contents?: true
Size: 927 Bytes
Versions: 12
Compression:
Stored size: 927 Bytes
Contents
Feature: `install' command with `-e' option
Scenario: describes `-e' option in the `install' command usage
When I successfully run `localeapp help install`
Then the output must match /-e.*--\[no-\]write-env-file.*write API key to/i
Scenario: writes API key to `.env' file when given `-e' option
Given I have a valid project on localeapp.com with api key "MYAPIKEY"
When I successfully run `localeapp install MYAPIKEY -e`
Then the file ".env" must contain exactly:
"""
LOCALEAPP_API_KEY=MYAPIKEY
"""
Scenario: preserves `.env' file content when given `-e' option
Given I have a valid project on localeapp.com with api key "MYAPIKEY"
And a file ".env" with content:
"""
FOO=BAR
"""
When I successfully run `localeapp install MYAPIKEY -e`
Then the file ".env" must contain exactly:
"""
FOO=BAR
LOCALEAPP_API_KEY=MYAPIKEY
"""
Version data entries
12 entries across 12 versions & 1 rubygems