Improve test coverage of our CalendarParser Java class about openrefine HOT 6 CLOSED

Can I work on this?

from openrefine.

I think going above 80% would be pretty nice already, but I have no idea how much work that involves.
Of course the goal would be to make actual assertions about the parsed values and not just trigger code paths for the sake of coverage. Let us know how it goes :)

from openrefine.

@shivam999876 something along those lines yes, but it would need to include quite a few more cases to reach a decent coverage. I would recommend we let @pkumar2001 have a go at this first, as I have assigned them to the issue already. Feel free to tackle another issue where no-one is assigned yet.

from openrefine.

what is the target test coverage?

from openrefine.

@wetneb Will the code work?
//Code to fix the issue.
import static org.junit.Assert.*;
import org.junit.Test;
import java.util.Calendar;

public class CalendarParserTest {

@Test
public void testParseValidDate() {
    CalendarParser parser = new CalendarParser();
    Calendar result = parser.parse("2024-03-20");
    assertNotNull(result);
    assertEquals(2024, result.get(Calendar.YEAR));
    assertEquals(Calendar.MARCH, result.get(Calendar.MONTH));
    assertEquals(20, result.get(Calendar.DAY_OF_MONTH));
}

@Test
public void testParseInvalidDate() {
    CalendarParser parser = new CalendarParser();
    Calendar result = parser.parse("invalid-date");
    assertNull(result);
}

@Test
public void testParseNullInput() {
    CalendarParser parser = new CalendarParser();
    Calendar result = parser.parse(null);
    assertNull(result);
}

}

from openrefine.

@wetneb Thanks for your response.

from openrefine.