Sha256: ba1e42a1e4365081ca1b3414a57052d8cebd1e65f914547515e77ff23207fe1b
Contents?: true
Size: 1.63 KB
Versions: 23
Compression:
Stored size: 1.63 KB
Contents
Feature: Pushing existing translation to localeapp
Scenario: Running push on a file
In order to send my translations
When I have a valid project on localeapp.com with api key "MYAPIKEY"
And an initializer file
And an empty file named "config/locales/en.yml"
When I run `localeapp push config/locales/en.yml`
Then the output should contain:
"""
Localeapp Push
Pushing file en.yml:
Success!
config/locales/en.yml queued for processing.
"""
And help should not be displayed
Scenario: Running push on a directory
In order to send my translations
When I have a valid project on localeapp.com with api key "MYAPIKEY"
And an initializer file
And an empty file named "config/locales/en.yml"
And an empty file named "config/locales/es.yml"
When I run `localeapp push config/locales`
Then the output should contain:
"""
Localeapp Push
Pushing file en.yml:
Success!
config/locales/en.yml queued for processing.
Pushing file es.yml:
Success!
config/locales/es.yml queued for processing.
"""
And help should not be displayed
Scenario: Running push on a file with no initializer file, passing the key on the command line
In order to send my translations
When I have a valid project on localeapp.com with api key "MYAPIKEY"
And an empty file named "config/locales/en.yml"
When I run `localeapp -k MYAPIKEY push config/locales/en.yml`
Then the output should contain:
"""
Localeapp Push
Pushing file en.yml:
Success!
config/locales/en.yml queued for processing.
"""
And help should not be displayed
Version data entries
23 entries across 23 versions & 1 rubygems