1.
Overview
2.
Framework
2.1.
Getting Started
2.2.
Your First Test
2.3.
Connecting Chainlink Node
2.4.
Connecting Chainlink Node (Multiple networks)
2.5.
NodeSet Environment
2.6.
NodeSet with Capabilities
2.7.
NodeSet (Local Docker builds)
2.8.
NodeSet Compat Environment
2.9.
Creating your own components
2.10.
Fork Testing
2.11.
Quick Contracts Deployment
2.12.
Verifying Contracts
2.13.
NodeSet with External Blockchain
2.14.
CLI
2.15.
Configuration
2.16.
Test Configuration
2.17.
Exposing Components
2.18.
Debugging Tests
2.19.
Components Cleanup
2.20.
Components Caching
2.21.
Mocking Services
2.22.
Copying Files
2.23.
External Environment
2.24.
Troubleshooting
2.25.
Secrets
2.26.
Observability Stack
2.26.1.
Metrics
2.26.2.
Logs
2.26.3.
Profiling
2.26.4.
Traces
2.27.
Blockscout
2.28.
Components
2.28.1.
Blockchains
2.28.1.1.
EVM
2.28.1.2.
Solana
2.28.1.3.
Optimism Stack
2.28.1.4.
Arbitrum Stack
2.28.2.
Chainlink
2.28.2.1.
Node
2.28.2.2.
NodeSet
2.29.
Clients
2.29.1.
Chainlink
2.29.2.
RPC
2.29.3.
Loki
3.
Testing Maturity Model
3.1.
Smoke
3.2.
Performance
3.3.
Chaos
4.
Interactive
5.
Libraries
5.1.
Seth
5.2.
WASP
5.2.1.
Getting started
5.2.2.
First test (RPS test)
5.2.3.
Stateful test
5.2.4.
User Journey test
5.2.5.
Profile test
5.2.6.
Testing alerts
5.2.7.
Configuration
5.2.8.
k8s
5.2.9.
Components
5.2.9.1.
Alert Checker
5.2.9.2.
Dashboard
5.2.9.3.
Generator
5.2.9.4.
Loki
5.2.9.5.
Profile
5.2.9.6.
Sampler
5.2.9.7.
Schedule
5.2.10.
BenchSpy
5.2.10.1.
Getting started
5.2.10.2.
Your first test
5.2.10.3.
Simplest metrics
5.2.10.4.
Standard Loki metrics
5.2.10.5.
Custom Loki metrics
5.2.10.6.
Standard Prometheus metrics
5.2.10.7.
Custom Prometheus metrics
5.2.10.8.
To Loki or not to Loki?
5.2.10.9.
Real world example
5.2.10.10.
Reports
5.2.10.10.1.
Standard Report
5.2.10.10.1.1.
Adding new QueryExecutor
5.2.10.10.1.2.
Adding new standard load metric
5.2.10.10.1.3.
Adding new standard resource metric
5.2.10.10.2.
Defining a new report
5.2.10.11.
Adding new storage
5.2.11.
How to
5.2.11.1.
Start local observability stack
5.2.11.2.
Try it out quickly
5.2.11.3.
Chose between RPS and VUs
5.2.11.4.
Define NFRs and check alerts
5.2.11.5.
Use labels
5.2.11.6.
Incorporate load tests in your workflow
5.2.11.7.
Reuse dashboard components
5.2.11.8.
Parallelize load
5.2.11.9.
Debug Loki errors
5.3.
Havoc
5.4.
K8s Test Runner
5.5.
Sentinel
6.
Releasing modules
7.
CTFv1 (Discouraged)
7.1.
Blockchain
7.2.
Concurrency
7.3.
Client
7.3.1.
Anvil
7.3.2.
AWS Secrets Manager
7.3.3.
Github
7.3.4.
Grafana
7.3.5.
Kafka
7.3.6.
Loki
7.3.7.
MockServer
7.3.8.
Postgres
7.3.9.
Prometheus
7.4.
Kubernetes
7.4.1.
Creating environments
7.4.2.
Using remote runner
7.4.3.
Passing test secrets
7.4.4.
chain.link labels
7.5.
Kubernetes (legacy docs)
7.5.1.
K8s Remote Run
7.5.2.
K8s Tutorial
7.6.
Config
7.7.
CRIB Connector
7.8.
Docker
7.8.1.
Blockchain nodes
7.8.2.
Chainlink ecosystem
7.8.3.
Third party apps
7.8.4.
Test helpers
7.9.
Logging
8.
Build info
Light
Rust
Coal
Navy
Ayu
Chainlink Testing Framework
Libraries
CTF monorepository contains a set of libraries:
WASP
- Scalable protocol-agnostic load testing library for
Go
Havoc
- Chaos testing library
Seth
- Ethereum client library with transaction tracing and gas bumping