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

Posted to commits@hudi.apache.org by "vinoyang (Jira)" <ji...@apache.org> on 2020/05/19 06:25:00 UTC

[jira] [Closed] (HUDI-203) Improve Unit Test Quality in Hudi

     [ https://issues.apache.org/jira/browse/HUDI-203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

vinoyang closed HUDI-203.
-------------------------
    Resolution: Implemented

> Improve Unit Test Quality in Hudi 
> ----------------------------------
>
>                 Key: HUDI-203
>                 URL: https://issues.apache.org/jira/browse/HUDI-203
>             Project: Apache Hudi (incubating)
>          Issue Type: Improvement
>          Components: Testing
>            Reporter: Balaji Varadarajan
>            Assignee: vinoyang
>            Priority: Minor
>
> Historically, We had been  tackling a CI problem - Tests taking too long to finish and timing out. We had mitigated this by eliminating redundant tests. and are introducing parallel jobs feature of travis ([https://docs.travis-ci.com/user/speeding-up-the-build/#parallelizing-your-builds-across-virtual-machines]) to have both unit and integration tests run in parallel. We realized that the unit-tests themselves needs to be refactored holistically. We would need to do a better job in standardizing the test setup utility functions and abstractions.  Also, some tests have huge setup costs but they don't need the entire setup.  This ticket is for tracking this effort.



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