[YUNIKORN-207] [Umbrella] Improve unit testing coverage

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Feedback Received
• Component/s: core - common, core - scheduler, shim - kubernetes, webapp
• Assignee: Unassigned
• Reporter: Weiwei Yang
• Created: 05/Jun/20 04:23
• Updated: 20/Nov/23 17:26
• Resolved: 20/Nov/23 17:26

Description

Pls take a look at [SpaceX lessons learned|https://lwn.net/Articles/540368/?from=groupmessage&isappinstalled=0]

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.

we should learn from how to build a rocket

Issue Links

• relates to: YUNIKORN-413 [Umbrella] Re-designing Yunikorn REST API's version 1

Sub-Tasks

• Increase unit test coverage for webservice.go: Closed
• Improve code coverage for application_events.go: Closed