Forcing the "test" experience about google-optimize-module HOT 3 OPEN

Why not set the weights accordingly based on the current environment you're in? e.g., using environment variables, etc.

I think this is kind of outside the scope. What do you think @hecktarzuli @pi0 ?

from google-optimize-module.

@farzadso Can you provide some more insight on how I might go about setting those environment variables? Do the experiments receive the context as an argument? Or are you simply talking about referencing process.env.TEST_A_WEIGHT within the experiments. The latter will not work as we build the application once using docker, then inject various environment specific variables.

Passing the context as an argument could be beneficial in that it would allow for different test id's within environments as well.

from google-optimize-module.

@t1mwillis I meant the latter and since you're using the same built image you can't achieve what I meant.

If your test environments have a specific URL structure, a hacky version would be to set the conditions based on the different URLs.

from google-optimize-module.