Skip to content

Conversation

@dimas-b
Copy link
Contributor

@dimas-b dimas-b commented Dec 31, 2024

This makes exception handling tests more direct and more light-weight. Previously FileIOIntegrationTest used the full DW application stack just to exercise some custom test code in runtime.

  • Validate the basic fact of storage-level exception propagation to the REST API layer in FileIOExceptionsTest.

  • Validate relevant I/O exception message handling and status codes in IcebergExceptionMapperTest.

  • IcebergExceptionMapper is implicitly engaged in runtime by the Web App framework based on its annotations.

This makes exception handling tests more direct and more
light-weight. Previously `FileIOIntegrationTest` used the
full DW application stack just to exercise some custom test
code in runtime.

* Validate the basic fact of storage-level exception propagation
  to the REST API layer in `FileIOExceptionsTest`.

* Validate relevant I/O exception message handling and status codes
  in `IcebergExceptionMapperTest`.

* `IcebergExceptionMapper` is implicitly engages in runtime by the Web App
  framework based on its annotations.
}

@Test
void testGetLengthExceptionSupplier() {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test case has been dropped completely, but in reality it used to test just other test code 🤷

@adutra adutra merged commit e548601 into apache:main Jan 2, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants