figure out how to pick up SE information from the runtime environment to eliminate the need to set it manually. Here is how TDA picks it up depending on whether it's running in production or being run locally by an SE. That won't work - we need to inject an environment variable when launching the simulator instead because you can't launch a shell process from a simulator like we do in python with id -un command. We will also need to figure out how to determine whether we are running inside an Appium VM and then set se=tda otherwise set it to system user like in conftest.py above (we probably won't have control over environment variables in SauceLabs unlike when launching simulator locally).
extend fingerprint in beforeSend to create separate issues for each SE and TDA (see e.g. flask)
Context and rationale: this allows us to guarantee someones local testing is not contaminating production issue even if they are using demo org instead of personal org for testing. Historically we have fond this hugely helpful to prevent confusion when debugging demo app issues in all of our other demo platforms.
Here is how TDA picks it up depending on whether it's running in production or being run locally by an SE.That won't work - we need to inject an environment variable when launching the simulator instead because you can't launch a shell process from a simulator like we do in python withid -uncommand. We will also need to figure out how to determine whether we are running inside an Appium VM and then setse=tdaotherwise set it to system user like in conftest.py above (we probably won't have control over environment variables in SauceLabs unlike when launching simulator locally).Context and rationale: this allows us to guarantee someones local testing is not contaminating production issue even if they are using
demoorg instead of personal org for testing. Historically we have fond this hugely helpful to prevent confusion when debugging demo app issues in all of our other demo platforms.