-
Notifications
You must be signed in to change notification settings - Fork 133
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
split up modules in a naive way. Next step is getting config split up…
… correctly.
- Loading branch information
Showing
8 changed files
with
394 additions
and
95 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Testing | ||
|
||
|
||
## Integration Tests | ||
|
||
### Troubleshooting Integration Tests | ||
|
||
#### `AggregateError` doesn't tell me what went wrong | ||
Wrap the "expect" statements of the offending test in a `try/catch` block and print the error like so: | ||
```javascript | ||
try { | ||
expect(foo).toEqual(bar); | ||
} catch (e) { | ||
console.log("Aggregate Error: ", e); | ||
} | ||
``` | ||
|
||
TODO: Maybe write a custom reporter | ||
|
||
#### I want to know what request the container actually received | ||
There are two options here: | ||
1. In the `afterAll` block, comment out the code that runs the container teardown. After the test fails, you can run `docker logs -f nginx-s3-gateway-test-base` | ||
|
||
2. Before the code that is erroring, add `timeout(3000)` then quickly run `docker logs -f nginx-s3-gateway-test-base` in another tab after the container starts. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.