Skip to content

Commit d6985d4

Browse files
committed
Update advanced_guide.md to clarify generator binding
Answers issues such as #200
1 parent 74c3af7 commit d6985d4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

advanced_guide.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ For how to write custom Python extensions, see the [extensions guide](extensions
2121
+ Generators **must be declared by name** in the TestSet config for them to be used
2222
+ Generator bindings evaluate once per HTTP call:
2323
- **Only once per Test**, and **multiple times for a Benchmark**
24-
+ Generator bindings only apply to the Test/Benchmark they are declared in. New values are generated only when the binding is evaluated.
24+
+ Generator bindings are re-evaluated (and a new value generated) every time they are declared in a Test/Benchmark. Once the value has been generated, it can be used in all subsequent tests (unless that variable is bound to something else).
2525
3. **Data may be extracted from the HTTP response body** with the 'extract_binds' element in a test.
2626
+ Note that if the request fails, the data cannot be set (nothing to work with)
2727
+ Currently, this is unsupported for benchmarks: using extraction doesn't make sense because benchmarks should be isolated.

0 commit comments

Comments
 (0)