VB.NET DateTime.Parse Default Culture Ambiguity in Integration Tests

Answer the question first

.NET does not provide a project‑ or assembly‑level default culture for DateTime.Parse. The only reliable way to guarantee deterministic parsing across environments is to supply an explicit CultureInfo (or an exact format) each time you parse, or to temporarily set the thread’s culture for the scope of the operation.

Confirmed facts

• DateTime.Parse(String) overload uses CultureInfo.CurrentCulture to interpret the input string.
• The thread culture is inherited from the OS, the test runner, or the CI agent and can differ between developer machines, build agents, and production.
• For a string like "01/02/2023" the result can be January 2 or February 1 depending on whether the culture uses MM/dd/yyyy or dd/MM/yyyy.
• The .NET documentation recommends supplying an explicit format or CultureInfo when the input format is fixed.

Likely explanation

Because the default overload is culture‑sensitive, integration tests that omit a culture argument will produce non‑deterministic results whenever the test runner’s locale changes. This leads to silent failures or data corruption when the parsed date is later used in business logic.

Steps to eliminate the ambiguity (only the steps needed for this case)

1. Capture the current culture at the start of the test (or test fixture) so it can be restored later:

   Dim originalCulture As CultureInfo = Thread.CurrentThread.CurrentCulture

2. Set a known culture** for the duration of the parsing operation. Use CultureInfo.InvariantCulture if the date strings are ISO‑like, or a specific culture (e.g., New CultureInfo("en-US")) that matches the expected format:

   Thread.CurrentThread.CurrentCulture = CultureInfo.InvariantCulture   ' or your chosen culture

3. Perform the parse** (you may still use the overload without IFormatProvider because the thread culture is now fixed):

   Dim dt As DateTime = DateTime.Parse(inputString)

4. Restore the original culture** after the parse to avoid leaking the change to other tests:

   Thread.CurrentThread.CurrentCulture = originalCulture

5. Optional – use an exact‑format parse** for maximum safety and to avoid any reliance on thread culture:

   Dim dt As DateTime = DateTime.ParseExact(inputString, "yyyy-MM-dd", CultureInfo.InvariantCulture)

Verification steps you can add to the CI pipeline

• Log or assert CultureInfo.CurrentCulture.Name before and after the culture‑setting block to confirm the expected culture is in effect.
• Run the same test twice in a single pipeline: once with the thread culture set to InvariantCulture and once with a different culture (e.g., fr-FR). The parsed DateTime values should be identical when using the fixed‑culture or ParseExact approach, demonstrating that the result is no longer culture‑dependent.
• If you prefer not to alter thread culture, replace every DateTime.Parse call with DateTime.ParseExact (or TryParseExact) using the exact format string and CultureInfo.InvariantCulture. Then verify that the parsed value is identical across all culture settings.