[Improvement]: Refactored MemorySizeTest.testUnitConversion to Parameterized Test

[Monilnarang]

Aim:

Improve the test code by avoiding code duplication, improving maintainability, and enhancing readability. By converting the test into a parameterized unit test, we reduce boilerplate code, make it easier to extend by simply adding new input values, and improve debugging by clearly identifying which test case fails instead of searching through individual assertions.

Why are the changes needed?

• In the test testUnitConversion of class MemorySizeTest the same order of method calls (getBytes, getKibiBytes, getMebiBytes, . . . ) are repeated multiple times with different inputs, making the test harder to maintain and extend.
• Multiple such clusters of the above method calls are cluttered together in one test, blurring the exact scope of this test.
• When a test fails, JUnit only shows which assertion failed, but not which specific input caused the failure.
• Adding new test cases requires copying and pasting the whole block instead of simply adding new data.

Brief change log

Parameterized testUnitConversion
This reduces duplication, allows easy extension by simply adding new value sets, and makes debugging easier as it clearly indicates which test failed instead of requiring a search through individual assertions.

Test Run report before changes:

Test Run report after changes:

How was this patch tested?

• Add some test cases that check the changes thoroughly including negative and positive cases if possible

• Add screenshots for manual tests if appropriate

• Run test locally before making a pull request

Documentation

• Does this pull request introduce a new feature? (yes / no)
  No
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)