Additional unit tests for generate-workflow

[bosesuneha]

Description

Added negative test cases for increasing test coverage of pkg/workflows/workflows.go

Fixes # (issue) Feature # (details)

Type of change

Please delete options that are not relevant.

• [x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a breaking change which will impact consuming tool(s).

• [x] Unit Tests
• [x] Local build

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules

[bosesuneha]

:shipit: 👍 Thanks for ping & LGTM. Long run, table-driven test are well recommended and for repetitive function output we could alway move to it but it will involve minor refactor. Example : https://gobyexample.com/testing-and-benchmarking

@Tatsinnit Thanks, will try to incorporate more table-driven tests going forward.