jiangxt2 opened a new issue, #14362:
URL: https://github.com/apache/gravitino/issues/14362

   ### What would you like to be improved?
   
   The Python client already has DTO, request, exception, and integration 
tests. As its API coverage grows, these tests would benefit from a focused 
mapping between representative public SDK behavior and the corresponding REST 
contracts.
   
   This would help identify gaps in request routing, serialization, response 
interpretation, and exception mapping without assuming that every existing 
operation is defective.
   
   Unity Catalog OSS includes real-service table creation and retrieval tests 
with field assertions, together with client initialization and cleanup tests. 
These provide useful examples of testing observable SDK behavior. [UC API 
tests](https://github.com/unitycatalog/unitycatalog/blob/35df64c579b94990d8d315e8d804b265f0a4ee58/clients/python/tests/test_table.py),
 [client lifecycle 
tests](https://github.com/unitycatalog/unitycatalog/blob/35df64c579b94990d8d315e8d804b265f0a4ee58/clients/python/tests/test_api_client.py)
   
   ### How should we improve?
   
   - Map representative public operations to existing REST contracts and tests, 
identifying genuinely missing cases or weak assertions before adding coverage.
   - Cover HTTP methods, encoded identifiers, request serialization, response 
interpretation, and exception mapping at observable boundaries.
   - Verify representative read and mutation round-trips against a matching 
Gravitino server with the backends required by the selected operations.
   - Reuse existing fixtures and feature-specific regression tests. Coordinate 
installed-distribution smoke checks with dependency compatibility work.
   - Document the tested SDK/server baseline and expected behavior so failures 
are actionable.
   
   Start with an explicit, bounded set of operations and extend coverage 
alongside SDK changes.
   
   Parent epic: #14334.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to