Latest News from the Thunders Product Team
New feature

Set the browser location and permissions of web runs

Ines avatar
Shared by Ines •

You can now decide how a web run answers when the site under test asks for the location of the browser, or asks to send notifications or to use the microphone or the camera. This helps when a site waits for the location before it continues, or when a flow depends on one of these permissions.

The group Browser location and permissions is in the advanced run settings of a web test: on the Web Run Settings tab of an environment, in the advanced settings of a test case, and in the Execution settings of a test set.

  • Browser location: choose Block to refuse the request at once, Default to report the position of the execution cluster, or Custom to enter a latitude and a longitude in decimal degrees.
  • Notifications, Microphone and Camera: choose Allow or Block. With Default, the run does not answer, and the site sees what the browser does by itself.
  • See a refused request in the run: when the run refuses a permission request, the step shows a Permission request refused alert. The message names the permission and the setting that changes the answer.

When no level of the run settings sets a value, the run blocks the location request. A custom position moves only the GPS position. The IP address and the timezone stay those of the execution cluster, so a site that compares them can refuse the user. Invalid coordinates stop the run before it starts.

#Sprint36