[
https://issues.apache.org/jira/browse/YUNIKORN-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Bacsko updated YUNIKORN-2149:
-----------------------------------
Description:
Currently, we directly use the event system to test the web service handler
functions.
This is not ideal because it results in a more complicated test code. For
example, in order to test {{EventSystem.IsEventTrackingEnabled()}}, we need to
modify and restore the configmap.
Solution: don't directly call {{events.GetEventSystem()}}, instead, use a
function variable that can be replaced by the tests. This greatly simplifies
testing.
was:
Currently, we directly use the event system to test the web service handler
functions.
This is not ideal because it results in a more complicated test code. For
example, in order to test {{EventSystem.IsEventTrackingEnabled()}}, we need to
modify and restore the configmap.
Solution: don't directly call {{eventSystem.GetEventSystem()}}, instead, use a
function variable that can be replaced by the tests. This greatly simplifies
testing.
> Simplify handler test cases by using the mock event system
> ----------------------------------------------------------
>
> Key: YUNIKORN-2149
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2149
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
>
> Currently, we directly use the event system to test the web service handler
> functions.
> This is not ideal because it results in a more complicated test code. For
> example, in order to test {{EventSystem.IsEventTrackingEnabled()}}, we need
> to modify and restore the configmap.
> Solution: don't directly call {{events.GetEventSystem()}}, instead, use a
> function variable that can be replaced by the tests. This greatly simplifies
> testing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
