[Bug]: DatrePicker-test.js react.lazy test should use waitFor()

[jt-helsinki]

Package

@carbon/react

Browser

Chrome

Package version

v11.49.0

React version

18.2.0

Description

The test "should initialize a calendar when using react.lazy" would be more robust if it used waitFor().

For example:

render(
        <React.Suspense fallback="Loading">
          <LazyDatePicker datePickerType="single">
            <LazyDatePickerInput
              placeholder="mm/dd/yyyy"
              labelText="Date Picker label"
              id="date-picker-simple"
            />
          </LazyDatePicker>
        </React.Suspense>
      );

      const labeledElement = await screen.findByLabelText('Date Picker label');
      expect(labeledElement).toBeInTheDocument();

becomes

const labeledElement = await waitFor(() => screen.findByLabelText('Date Picker label'), { timeout: 10000 });

Reproduction/example

n/a

Steps to reproduce

Not consistent. Run the tests in CI mode and the error intermittently.

Suggested Severity

None

Application/PAL

No response

Code of Conduct

• I agree to follow this project's Code of Conduct
• I checked the current issues for duplicate problems