Improve empty browser string flag handling

[inancgumus]

What?

In v1.5.1, passing a string flag without a value results in an invalid argument that ends with an equal sign. For example:

K6_BROWSER_ARGS=disable-site-isolation-trials

Produces the following argument that we pass while launching the browser:

disable-site-isolation-trials=

It should be:

disable-site-isolation-trials

Why?

Having a superfluous suffix (=) prevents browsers (e.g., Chrome) from interpreting the argument, making the argument defunct.

How?

Handle the argument correctly here.

Tasks

Tasks

Beta Give feedback

1. Fix browser empty string flag parsing #1386
   bug +1
   
2. Update the k6 release notes

Related PR(s)/Issue(s)

No response