From c47a726c0ad002dfe63784d22c539ce787515770 Mon Sep 17 00:00:00 2001 From: Leonid Belenkiy Date: Mon, 15 Apr 2024 12:56:23 +0200 Subject: [PATCH] Solve the ext. validation unit test issue Signed-off-by: Leonid Belenkiy --- _posts/2024-03-30-vro-how-to-use-external-validations.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/_posts/2024-03-30-vro-how-to-use-external-validations.md b/_posts/2024-03-30-vro-how-to-use-external-validations.md index f10be37..5218eb5 100644 --- a/_posts/2024-03-30-vro-how-to-use-external-validations.md +++ b/_posts/2024-03-30-vro-how-to-use-external-validations.md @@ -98,6 +98,10 @@ Now let's run the same workflow, but in that time, we provide the name of the VM > > Despite my efforts, I could not find a way to do so. If you happen to find a solution, please feel free to share it in the comments section. +### Update 1 + +The problem regarding unit testing has been resolved and the solution can be accessed [here](https://github.com/unbreakabl3/vmware_aria_orchestrator_examples/blob/main/general_examples/src/test/validateVM.test.ts) + ## Summary The external validation can significantly reduce the risk of errors, improve the quality of the user's experience, and ensure that the workflow's outcome meets the user's expectations.