From ee5f1dc879da418209420883a1ebc9d99cf4ce72 Mon Sep 17 00:00:00 2001
From: Hariom Balhara <hariombalhara@gmail.com>
Date: Thu, 1 May 2025 12:35:12 +0530
Subject: [PATCH] fix unit test bug (#21046)

---
 .../calendars/__tests__/NoAvailabilityDialog.test.tsx        | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/packages/features/calendars/__tests__/NoAvailabilityDialog.test.tsx b/packages/features/calendars/__tests__/NoAvailabilityDialog.test.tsx
index 4d047d7708..c1f80923f2 100644
--- a/packages/features/calendars/__tests__/NoAvailabilityDialog.test.tsx
+++ b/packages/features/calendars/__tests__/NoAvailabilityDialog.test.tsx
@@ -95,7 +95,7 @@ describe("NoAvailabilityOverlay", () => {
     expect(defaultProps.nextMonthButton).toHaveBeenCalled();
   });
 
-  test("Displays 'View next month' and close buttons, without description, when browsing current date with rolling 30-day period", () => {
+  test("Displays 'View next month' and close buttons, without description, when browsing current date with rolling 32-day period", () => {
     render(
       <NoAvailabilityDialog
         {...defaultProps}
@@ -103,7 +103,8 @@ describe("NoAvailabilityOverlay", () => {
         periodData={{
           ...defaultProps.periodData,
           periodType: "ROLLING",
-          periodDays: 30,
+          // 32 days means that next month would atleast have 1 day available, so future limit violation isn't there and no description is shown
+          periodDays: 32,
         }}
       />
     );