You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Weiwei Yang (Jira)" <ji...@apache.org> on 2020/08/25 22:24:00 UTC

[jira] [Updated] (YUNIKORN-207) [Umbrella] Improve unit testing coverage

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

Weiwei Yang updated YUNIKORN-207:
---------------------------------
    Summary: [Umbrella] Improve unit testing coverage  (was: Improve unit testing coverage)

> [Umbrella] Improve unit testing coverage
> ----------------------------------------
>
>                 Key: YUNIKORN-207
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-207
>             Project: Apache YuniKorn
>          Issue Type: Improvement
>          Components: core - cache, core - common, core - scheduler, shim - kubernetes, webapp
>            Reporter: Weiwei Yang
>            Assignee: Adam Antal
>            Priority: Major
>
> Pls take a look at [SpaceX lessons learned|[https://lwn.net/Articles/540368/?from=groupmessage&isappinstalled=0]]
> {quote}
> Automation is important, and continuous integration is "very valuable", Rose said. He suggested building for every platform all of the time, even for "things you don't use any more". SpaceX does that and has found interesting problems when building unused code. Unit tests are run from the continuous integration system any time the code changes. "Everyone here has 100% unit test coverage", he joked, but running whatever tests are available, and creating new ones is useful.
> {quote}
> we should learn from how to build a rocket :)



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org