iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update README

This commit is contained in:
Mitchell Hashimoto 2013-12-12 13:44:16 -08:00
parent bec978fd8b
commit a4b6a5a341
1 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
test/README.md
View File

@ -12,7 +12,9 @@ real-world cost associated with running the tests. Be aware of that prior
to running the tests. Additionally, many tests will leave left-over artifacts to running the tests. Additionally, many tests will leave left-over artifacts
(AMIs) that you'll have to manually clean up. (AMIs) that you'll have to manually clean up.
## Required Software ## Running Tests
### Required Software
Before running the tests, you'll need the following installed. If you're Before running the tests, you'll need the following installed. If you're
running on Mac OS X, most of these are available with `brew`: running on Mac OS X, most of these are available with `brew`:
@ -21,7 +23,7 @@ running on Mac OS X, most of these are available with `brew`:
* [AWS cli](http://aws.amazon.com/cli/) * [AWS cli](http://aws.amazon.com/cli/)
## Configuring Tests ### Configuring Tests
**For tests that require AWS credentials:** **For tests that require AWS credentials:**
@ -30,7 +32,7 @@ Set the following self-explanatory environmental variables:
* `AWS_ACCESS_KEY_ID` * `AWS_ACCESS_KEY_ID`
* `AWS_SECRET_ACCESS_KEY` * `AWS_SECRET_ACCESS_KEY`
## Running Tests ### Running
These tests are meant to be run _one file at a time_. There are some These tests are meant to be run _one file at a time_. There are some
test files (such as the amazon-chroot builder test) that simply won't test files (such as the amazon-chroot builder test) that simply won't
@ -40,3 +42,10 @@ never work.
If you're working on Packer and want to test that your change didn't If you're working on Packer and want to test that your change didn't
adversely affect something, try running only the test that is related to adversely affect something, try running only the test that is related to
your change. your change.
```
$ bats builder_amazon_ebs.bats
```
Note: Working directory doesn't matter. You can call the bats test file
from any directory.