-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
docs update
- Loading branch information
Showing
14 changed files
with
179 additions
and
33 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
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,23 @@ | ||
# Components Cleanup | ||
|
||
Managing state is challenging, especially in end-to-end testing, we use [ryuk](https://golang.testcontainers.org/features/garbage_collector/#ryuk) and following simple rules: | ||
- If `TESTCONTAINERS_RYUK_DISABLED=true`, no cleanup occurs — containers, volumes, and networks remain on your machine. | ||
|
||
Feel free to use `ctf d rm` to remove containers when you are ready. | ||
- If `TESTCONTAINERS_RYUK_DISABLED` is unset, the test environment will be automatically cleaned up a few seconds after the test completes. | ||
|
||
|
||
Keep in mind that all components are mapped to [static ports](state.md), so without cleanup, only one environment can run at a time. | ||
|
||
This design choice simplifies debugging. | ||
|
||
A simplified command is available to prune unused volumes, containers, and build caches. Use it when you’re running low on space on your machine. | ||
``` | ||
ctf d c | ||
``` | ||
|
||
<div class="warning"> | ||
|
||
The framework manages cleanup for both on-chain and off-chain Docker components. However, if your test involves actions like configuring Chainlink jobs, it's best practice to make these actions idempotent, so they can be applied reliably in any environment. | ||
|
||
</div> |
This file was deleted.
Oops, something went wrong.
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
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
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 |
---|---|---|
@@ -1,19 +1,17 @@ | ||
# Intro | ||
|
||
The Chainlink Testing Framework (CTF) is a blockchain development framework written in Go. | ||
|
||
Its primary purpose is to help Chainlink developers create extensive integration, e2e, performance, and chaos tests to ensure the stability of the Chainlink project. | ||
|
||
It can also be helpful to those who just want to use Chainlink oracles in their projects to help test their contracts, or even for those that aren't using Chainlink. | ||
The Chainlink Testing Framework is a toolset designed for end-to-end testing of Chainlink products, focusing on functionality, resiliency, and performance. | ||
|
||
This documentation is primarily for: | ||
- Engineers looking to write end-to-end tests | ||
- Non-technical users or external developers who want to [setup](framework/interactive.md) `Chainlink` nodes locally | ||
This documentation is intended for: | ||
- Chainlink engineers writing end-to-end tests in [Golang](https://go.dev/) | ||
- Engineers using other languages who want to integrate with the Chainlink platform | ||
|
||
To get started with writing tests, refer to the [Framework](./framework/getting_started.md) chapter, where we guide you from basic to more complex scenarios. | ||
|
||
If you want to build integration with Chainlink not in [Golang](https://go.dev/), please refer to our [Interactive](framework/interactive.md) chapter. | ||
|
||
[Repository](https://github.com/smartcontractkit/chainlink-testing-framework) contains two major pieces: | ||
- [Framework](framework/overview.md) | ||
- [Libraries](libraries.md) | ||
|
||
If you're a non-technical user or want to build integration with Chainlink not in `Golang`, please refer to our [Interactive](framework/interactive.md) chapter. |
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,4 @@ | ||
- Add upgrade tests | ||
- Polish docs, add "cleanup" section | ||
- Add official CL images for 2.16, 2.17 + ARM versions | ||
- Do not fail if there is no default DB volume when cleanup |
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
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
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
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 |
---|---|---|
@@ -1,7 +1,7 @@ | ||
export TESTCONTAINERS_RYUK_DISABLED=true | ||
export PRIVATE_KEY="..." | ||
# load test | ||
export LOKI_TENANT_ID=promtail | ||
export LOKI_URL=http://localhost:3030/loki/api/v1/push | ||
#export LOKI_TENANT_ID=promtail | ||
#export LOKI_URL=http://localhost:3030/loki/api/v1/push | ||
#export RESTY_DEBUG=true | ||
export CTF_LOG_LEVEL=debug | ||
export CTF_LOG_LEVEL=info |
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
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.