features/jekyll-s3.feature in jekyll-s3-0.0.5 vs features/jekyll-s3.feature in jekyll-s3-0.0.6
- old
+ new
@@ -2,84 +2,28 @@
In order to push my jekyll site to s3
As a blogger
I want to run jekyll-s3 and say OMG it just worked!
- Scenario: Run jekyll-s3 in the wrong directory
- When I run `jekyll-s3`
- Then the output should contain:
- """
- I can't find any directory called _site. Are you in the right directory?
- """
+ @new-files
+ Scenario: Push a new Jekyll site to S3
+ When my Jekyll site is in "features/support/test_site_dirs/my.blog.com"
+ Then jekyll-s3 will push my blog to S3
+ And report that it uploaded 2 new and 0 changed files into S3
- Scenario: Run jekyll-s3 for the first time
- Given a directory named "_site"
- When I run `jekyll-s3`
- Then the output should contain:
- """
- I've just generated a file called _jekyll_s3.yml. Go put your details in it!
- """
- Then the file "_jekyll_s3.yml" should contain:
- """
- s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
- s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
- s3_bucket: your.blog.bucket.com
- """
+ @new-and-changed-files
+ Scenario: Upload a new blog post and change an old post
+ When my Jekyll site is in "features/support/test_site_dirs/new-and-changed-files.com"
+ Then jekyll-s3 will push my blog to S3
+ And report that it uploaded 1 new and 1 changed files into S3
- Scenario: Run jekyll-s3 with an empty configuration file
- Given a directory named "_site"
- And an empty file named "_jekyll_s3.yml"
- When I run `jekyll-s3`
- Then the output should contain:
- """
- I can't parse the file _jekyll_s3.yml. It should look like this:
- s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
- s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
- s3_bucket: your.blog.bucket.com
- """
+ @only-changed-files
+ Scenario: Update an existing blog post
+ When my Jekyll site is in "features/support/test_site_dirs/only-changed-files.com"
+ Then jekyll-s3 will push my blog to S3
+ And report that it uploaded 0 new and 1 changed files into S3
- Scenario: Run jekyll-s3 with a malformed configuration file
- Given a directory named "_site"
- And a file named "_jekyll_s3.yml" with:
- """
- s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
- this is not yaml
- """
- When I run `jekyll-s3`
- Then the output should contain:
- """
- I can't parse the file _jekyll_s3.yml. It should look like this:
- s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
- s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
- s3_bucket: your.blog.bucket.com
- """
-
- Scenario: Run jekyll-s3 with a configuration file that does not contain a bucket
- Given a directory named "_site"
- And a file named "_jekyll_s3.yml" with:
- """
- s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
- s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
- s3_bucket:
- """
- When I run `jekyll-s3`
- Then the output should contain:
- """
- I can't parse the file _jekyll_s3.yml. It should look like this:
- s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
- s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
- s3_bucket: your.blog.bucket.com
- """
-
- Scenario: Run jekyll-s3
- Given a directory named "_site"
- And a file named "_jekyll_s3.yml" with:
- """
- s3_id: YOUR_AWS_S3_ACCESS_KEY_ID
- s3_secret: YOUR_AWS_S3_SECRET_ACCESS_KEY
- s3_bucket: your.blog.bucket.com
- """
- When I run `jekyll-s3`
- Then the output should contain:
- """
- Deploying _site/* to your.blog.bucket.com
- """
+ @no-new-or-changed-files
+ Scenario: The user runs jekyll-s3 even though he doesn't have new or changed posts
+ When my Jekyll site is in "features/support/test_site_dirs/no-new-or-changed-files.com"
+ Then jekyll-s3 will push my blog to S3
+ And report that it uploaded 0 new and 0 changed files into S3