You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: book/src/framework/test_configuration_overrides.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,3 +68,14 @@ This helps reduce duplication in the configuration.
68
68
69
69
> [!WARNING]
70
70
> When override slices remember that you should replace the full slice, it won't be extended by default!
71
+
72
+
## Overriding Components Configuration
73
+
74
+
The same override logic applies across components, files, and configuration fields in code, configs are applied in order:
75
+
76
+
1. Implicit component defaults that are defined inside application
77
+
2. Component defaults defined in the framework or external component, ex.: [CLNode](https://github.com/smartcontractkit/chainlink-testing-framework/blob/main/framework/components/clnode/default.go)
78
+
3.`Test.*Override`
79
+
4.`user_.*_overrides`
80
+
81
+
Use `Test.*Override` in test `code` to override component configurations, and `user_.*_overrides` in `TOML` for the same purpose.
0 commit comments