Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
packer
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kristopher Ruzic
packer
Commits
a4b6a5a3
Commit
a4b6a5a3
authored
Dec 12, 2013
by
Mitchell Hashimoto
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update README
parent
bec978fd
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
3 deletions
+12
-3
test/README.md
test/README.md
+12
-3
No files found.
test/README.md
View file @
a4b6a5a3
...
...
@@ -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
(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
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/
)
## Configuring Tests
##
#
Configuring Tests
**For tests that require AWS credentials:**
...
...
@@ -30,7 +32,7 @@ Set the following self-explanatory environmental variables:
*
`AWS_ACCESS_KEY_ID`
*
`AWS_SECRET_ACCESS_KEY`
##
Running Tests
##
# Running
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
...
...
@@ -40,3 +42,10 @@ never work.
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
your change.
```
$ bats builder_amazon_ebs.bats
```
Note: Working directory doesn't matter. You can call the bats test file
from any directory.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment