You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Nikolay Izhikov (Jira)" <ji...@apache.org> on 2020/01/25 09:53:00 UTC

[jira] [Created] (IGNITE-12581) [REFACTORING] Test parametrization

Nikolay Izhikov created IGNITE-12581:
----------------------------------------

             Summary: [REFACTORING] Test parametrization
                 Key: IGNITE-12581
                 URL: https://issues.apache.org/jira/browse/IGNITE-12581
             Project: Ignite
          Issue Type: Improvement
            Reporter: Nikolay Izhikov


Right now many Ignite tests parametrization implemented via inheritance.

For example:

parent - JdbcThinBulkLoadAbstractSelfTest

extensions - JdbcThinBulkLoadAtomicPartitionedNearSelfTest, 

JdbcThinBulkLoadAtomicPartitionedSelfTest, 

JdbcThinBulkLoadAtomicReplicatedSelfTest, 

JdbcThinBulkLoadTransactionalPartitionedNearSelfTest, 

JdbcThinBulkLoadTransactionalPartitionedSelfTest, 

JdbcThinBulkLoadTransactionalReplicatedSelfTest.

 

Look like we can significantly reduce tests code base, therefore, improve readability and maintainability without losing any test-cases if we use the JUnit parameterized approach.

 

A contributor can use this ticket as an umbrella one and create a sub-ticket for each refactored test-classes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)