Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provider should expand unit test coverage #1206

Open
rquitales opened this issue Jun 20, 2024 · 0 comments
Open

Provider should expand unit test coverage #1206

rquitales opened this issue Jun 20, 2024 · 0 comments
Labels
area/testing kind/engineering Work that is not visible to an external user kind/enhancement Improvements or new features

Comments

@rquitales
Copy link
Contributor

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

This provider should leverage more on unit tests to expand coverage. Some areas we can attempt to test are:
a) user inputs and ensuring that combinations of inputs are supported
b) ensuring the individual components/resources created are accurate

This will help improve confidence in code changes while driving down testing time.

Affected area/feature

Nodejs provider code

@rquitales rquitales added area/testing kind/enhancement Improvements or new features kind/engineering Work that is not visible to an external user labels Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing kind/engineering Work that is not visible to an external user kind/enhancement Improvements or new features
Projects
None yet
Development

No branches or pull requests

1 participant