Work with VU.State.Options to validate browser options

[ankur22]

Once the browser options are part of scenarios, we need to be able to validate the options and the env vars. Options should be possible to validate with the use of VU.State.Options. One thing to keep in mind is whether we can validate options and env vars before the test run starts so that we can error out and warn users as early as possible.

[ka3de]

Hey @imiric , one question, in relation with this issue and the work done in grafana/k6@948587b. Are we missing a new method definition in the ExecutorConfig interface to be able to retrieve the newly created ScenarioOptions from executors BaseConfig ?

Also, I have one doubt. From VU.State().Options I understand we will be able to get all the options that are set for the test run (when solving first comment or casting to BaseConfig), including all the scenario options. But, from k6 browser perspective, how can we know to which scenario does the current VU execution belong to?
So basically, from what I understand, k6 browser is initiated per VU passing the k6 modules.VU struct. But how can we correlate that with the specific scenario that that VU belongs to?

[imiric]

@ka3de: You're right. A method on ExecutorConfig to retrieve the options would be helpful, as otherwise you'd need to type assert all possible implementations 😅. I also ran into this when I wanted to add some tests for this field... I'll add the method later today.

Re: your second question, you should be able to get the scenario name the VU is running in in the same way as it's done in the k6/execution module. Then you can get the options only for that scenario.

There should be a friendlier API for this eventually, but this will have to do for now.

[ka3de]

Great. Thank you @imiric , and thank you for the example on how to correlate the VU with the scenario 👍