ATLAS-5245: fix unittest failures in EntitySearchProcessorTest

[mneethiraj]

What changes were proposed in this pull request?

updated EntitySearchProcessorTest to use Calendar.getInstance(utcTimeZone), to match the timezone used in SearchProcessor.processDateRange().

How was this patch tested?

verified that unit test failures in EntitySearchProcessorTest are resolved.

[Copilot]

Pull request overview

Updates EntitySearchProcessorTest to align date-range expectations with the UTC-based behavior in SearchProcessor.processDateRange(), addressing timezone-dependent unit test failures.

Changes:

• Introduced a shared TIME_ZONE_UTC constant for reuse in test date calculations.
• Set FORMATTED_DATE to UTC using the shared constant.
• Switched several date-range tests from Calendar.getInstance() to Calendar.getInstance(TIME_ZONE_UTC) for UTC-consistent expected values.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[jackhalfalltrades]

Looks good

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

repository/src/test/java/org/apache/atlas/discovery/EntitySearchProcessorTest.java:460

• testYesterday() only asserts the first value from the returned time-range (start). Since processDateRange() returns a start and end timestamp, this test should also assert the end value to catch off-by-one/end-of-day regressions.

        String[] dates      = ret.getAttributeValue().split(",");
        String   attrValue1 = dates[0];

        assertEquals(FORMATTED_DATE.format(new Date((Long.parseLong(attrValue1)))), FORMATTED_DATE.format(yesterdayDate.getTime()));
    }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.