Iurii Gerzhedovich created IGNITE-21536:
-------------------------------------------
Summary: Improve test coverage for Table Views
Key: IGNITE-21536
URL: https://issues.apache.org/jira/browse/IGNITE-21536
Project: Ignite
Issue Type: Improvement
Components: general
Reporter: Iurii Gerzhedovich
During implementation Table Views functionality were added set of tests.
However added set of tests is insufficient.
Let's add the following test scenarios:
h3. * Unit Testing
* Working of Mappers for all supported types
* Default mappings for all supported types
* Testing of projections including empty projection, null, unnecessary fields,
not a complete set of fields
* Set of fields in projection with right names but not matching types
(including different type of collections and custom classes)
* Projections for classes with different modifiers like
final/static/strictfp/volatile/transient
h3. * Functional and End-to-End Testing
Need to make sure that any modification of the underlying table is reflected
in the result of RecordView and KeyValueView. So after creating the table, we
need to go through various operations (add/drop/change type/default column) and
check that all changes are reflected in the result.
Let's check the operation of both RecordView and KeyValueView for auto
generated keys.
Check the operation of Views’s for different registers is the same as we have
in underlying tables for mappers and for projections.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
