feat(version-tests): Add comprehensive API coverage to TagsTester

[Liljis]

Description

Expanded the version compatibility tests in TagsTester.java to include comprehensive API coverage beyond just the convert source endpoint, as requested in #134.

Changes Made

Added 5 new test methods to doConversion() in TagsTester.java:

1. testConvertWithMultipleFormats - Tests conversion with MARKDOWN, JSON, and TEXT output formats ( already existed, done only refactoring)

2. testConvertWithJsonFormat - Validates JSON output and DoclingDocument deserialization

• Requests only JSON format
• Tests: "Can we properly deserialize the JSON into a DoclingDocument Java object?"
• Validates: The JSON structure is correct and can be parsed into the Java class
• Checks: Specific fields like getName() work correctly

3. testConvertWithDifferentOptions - Tests conversion with OCR, images, table mode, and custom timeout

• Extracts text from images in the document
• Embeds or references images in the converted output
• Controls how tables are extracted and formatted
• Sets maximum time for document processing

4. testClearConverters - Tests the /v1/clear/converters endpoint

• Clears cached converter instances (PDF parsers, OCR engines, etc.)

5. testClearResults - Tests the /v1/clear/results endpoint

• Clears cached conversion results (the actual converted documents)

Motivation

The previous implementation only tested the basic convert source API. This enhancement provides:

• Better coverage of the Docling Serve API surface
• Validation of multiple endpoints (health, convert, clear)
• Testing of various conversion options and output formats
• More comprehensive compatibility checks across versions

Test Results

• Build successful with no compilation errors
• All v1.x versions (v1.0.0+) pass all 6 tests
• v0.x versions fail as expected (AP
  results.md

[edeandrea]

Thanks @Liljis for this! See comments in-line.

The comments about "spelling out" the full class name apply in other places I saw. We can just import the classes.

Also, do you consider this PR complete? I was hoping to get some tests of more than just the convertSource operation too. Some of the async operations, chunking, etc.

Its fine either way. We can certainly "baby step" adding more tests, but I'm not going to consider #134 as "complete" until more tests of the other operations are added as well.

FWIW there are other unit tests in https://github.com/docling-project/docling-java/blob/main/docling-serve/docling-serve-client/src/test/java/ai/docling/serve/client/AbstractDoclingServeClientTests.java that can be "borrowed" and re-implemented here.

[edeandrea]

We shouldn't need to "spell out" the entire import ai.docling.serve.api.convert.response.ResponseType? Just

.isEqualTo(ResponseType.IN_BODY);

[edeandrea]

We shouldn't need to "spell out" the entire import ai.docling.serve.api.convert.request.options.TableFormerMode? Just

.tableMode(TableFormerMode.FAST)

[edeandrea]

Also, before I can merge this, can you please ensure both the DCO check and the semantic PR check passes? You may need to ammend your commit and do a signoff.

[github-actions]

:java_duke: JaCoCo coverage report

Overall Project	46.79%	🔴

There is no coverage information present for the Files changed

[github-actions]

	Tests	Passed ✅	Skipped	Failed
Gradle Test Results (all modules & JDKs)	1002 ran	1002 passed	0 skipped	0 failed

Test	Result
No test annotations available

• View Gradle Test Results (all modules & JDKs)

[github-actions]

HTML test reports are available as workflow artifacts (zipped HTML).

• Download: Artifacts for this run