Commit 45a71925 authored by Dallas Reedy's avatar Dallas Reedy

Fix GLEX testing examples: on_any_instance => on_next_instance

parent 0cf05541
...@@ -492,12 +492,12 @@ expect(subject).to track(:my_event) ...@@ -492,12 +492,12 @@ expect(subject).to track(:my_event)
subject.track(:my_event) subject.track(:my_event)
``` ```
You can use the `on_any_instance` chain method to specify that it could happen on You can use the `on_next_instance` chain method to specify that it will happen
any instance of the experiment. This helps you if you're calling on the next instance of the experiment. This helps you if you're calling
`experiment(:example).track` downstream: `experiment(:example).track` downstream:
```ruby ```ruby
expect(experiment(:example)).to track(:my_event).on_any_instance expect(experiment(:example)).to track(:my_event).on_next_instance
experiment(:example).track(:my_event) experiment(:example).track(:my_event)
``` ```
...@@ -506,7 +506,7 @@ A full example of the methods you can chain onto the `track` matcher: ...@@ -506,7 +506,7 @@ A full example of the methods you can chain onto the `track` matcher:
```ruby ```ruby
expect(experiment(:example)).to track(:my_event, value: 1, property: '_property_') expect(experiment(:example)).to track(:my_event, value: 1, property: '_property_')
.on_any_instance .on_next_instance
.with_context(foo: :bar) .with_context(foo: :bar)
.for(:variant_name) .for(:variant_name)
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment