Uniformity in Testing Patterns

[amritanshusikdar]

Description The testing patterns in this repository have been a bit inconsistent. We're specifically talking about unit testing here. Below is an instance:

• The scaffold validate() function is package private because it is used only for the scaffold command as an internal functionality. But this takes away from the unit testability:
  • This function is hence tested here
• The new create command layer also has a Validate() function, which in contrast to the scaffold command is public and includes a corresponding options_test.go file with unit tests solely for this function.

Reasons

• There should be consistency with the testing patterns
• There should be uniformity across team ideologies, hence something like this could also be implemented here

Acceptance Criteria

• [ ] The unit tests for scaffold command are adjusted to follow the same pattern as the create command
• [ ] Appropriate changes are done in the e2e tests as well

[github-actions[bot]]

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed due to the lack of recent activity. /lifecycle rotten