How Is Browser Time Determined in Automated Test Runs?

Nextworld Platform
1

Hi all, I’m looking for some clarification around how timezones are handled during automated suite execution.

While debugging a date-related issue, I noticed the following behavior:

  • In my LC, when following best practices (using the date data item and defaulting the date from app settings), the date always defaulted correctly based on browser time during manual testing.

  • However, during automated suite runs, the timestamp shown at the bottom of the app is UTC.

  • Despite this, the date defaulted inside the app reflects the tenant’s timezone (Denver).

  • This creates a mismatch where the UI timestamp is UTC, but the app logic is defaulting the date based on Denver time.

Is there anyone from the Tools team who can help verify how browser time is determined during suite runs, and why we’re seeing a mix of UTC timestamps and tenant-time date defaults?

image
image1920×1110 186 KB

2

Hi @pradeep.das, can you log back into that temp tenant (if it’s been preserved) when you have a chance and look for the following information?

  • Navigate to User Profile in the top right corner (Michael for this temp tenant)
  • Navigate to the 4th page titled “Locale”
    • Is the value for Custom Time Zone selected or not selected, and if selected, what is the custom time zone that has been entered?
  • Navigate (if accessible) to the Tenant Environment Setup application and go to the Environment step in the composite
    • Is there a row, and if so, is there a value for either Display Preferred Time Zone or Time Zone?

It looks like the test suite is potentially running with a tenant/environment time zone of Denver and a browser time zone of UTC, but we can’t know for certain without looking for those values. Populating a value of “Today” or “mm/dd/yyyy” with an app setting should use the browser time zone unless either Display Preferred Time Zone or Use Custom Time Zone is true.

Can you also provide some more information on how the date is being defaulted, whether this is definitely a Date and not a DateTime field, and whether there’s any logic blocks involved rather than the data mapper or an app setting?

I was not able to reproduce this issue where the Date defaulted into an application was different than the current date according to the NW Footer - date should always match that value as that is the user’s time zone.

3

Hi @ross , here are the details:

  • Custom Time Zone in the User Profile (Locale page) is not selected.

  • In the Tenant Environment Setup → Environment step, there is no row present, so no values exist for Display Preferred Time Zone or Time Zone.

  • The date is being defaulted using an App Setting (Application Setting Definition → Field Mapping).

  • It is a Date field, not a DateTime field.

  • There are no logic blocks involved, defaulting is purely through the app setting.

I’m also not able to reproduce this manually. The issue only appears when running the automated suite. Manually, the date always matches the NW footer time as expected.

Let me know if you need any other details or want me to test additional scenarios.

image
image1550×725 44.6 KB

image
image1557×876 159 KB

image
image1549×875 198 KB

4

Thank you for the follow-up information @pradeep.das!

Per the settings that have been established in that test tenant, the date, time, and time zone displayed on the footer should always match the time zone that the user is in. That time zone is determined based on where the user physically is according to their browser.
Data entry should always abide by that time zone, so the app setting’s mapping of System -> Today should mean whatever “Today” is in the current user’s browser time. Per the original post and screenshot, “Today” should have entered the value November 13, 2025.

This is a bug. Can you please work with support to create a ticket and include reference to this post?

1 Like