Skip to content
New issue

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

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

Already on GitHub? # to your account

Re-factor our test to have a consistent coding standard #1481

Closed
jellypuno opened this issue Sep 9, 2021 Discussed in #1480 · 3 comments
Closed

Re-factor our test to have a consistent coding standard #1481

jellypuno opened this issue Sep 9, 2021 Discussed in #1480 · 3 comments
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have Technical Debt Includes Architecture, Code, Testing, Automation debt

Comments

@jellypuno
Copy link
Contributor

Discussed in #1480

Originally posted by jellypuno September 9, 2021
Currently our tests have 2 different coding standard. (please see ZoweUSSNode.unit.test.ts and dataset>actions.unit.test) Let's factor the unit test once again to make the coding consistent. Also, the extensible API are not mocked properly. Let's check our tests and make sure that they are mocked properly.

@jellypuno jellypuno added the Technical Debt Includes Architecture, Code, Testing, Automation debt label Sep 9, 2021
@jellypuno jellypuno changed the title Re-factor our test to have one consistent coding standard Re-factor our test to have a consistent coding standard Sep 9, 2021
@JillieBeanSim
Copy link
Contributor

Captured from #1028

  • Test for API package test:
    • Initialization
    • Profile Loading
  • Moving all to parent unit test package so it could be re-used by other packages
  • Refactoring of Integration Test

@zFernand0 zFernand0 added the priority-low Legit issue but cosmetic or nice-to-have label Oct 5, 2022
@zFernand0 zFernand0 added the enhancement New feature or request label Jan 5, 2023
@github-actions
Copy link

github-actions bot commented Jan 5, 2023

Thank you for raising this issue.
The community has 90 days to upvote 👍 the issue.
If it receives 10 upvotes, we will move it to our backlog. If not, we will close it.

@JillieBeanSim
Copy link
Contributor

This enhancement has had no community activity for 12 months. The issue also has less than 10 up-votes by the community. No action on this enhancement is targeted for the next 2 calendar quarters. Therefore, this enhancement is being closed. If you feel that this enhancement should continue to be available for community up-votes, you may reopen this issue.

@JillieBeanSim JillieBeanSim closed this as not planned Won't fix, can't repro, duplicate, stale Apr 27, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request priority-low Legit issue but cosmetic or nice-to-have Technical Debt Includes Architecture, Code, Testing, Automation debt
Projects
None yet
Development

No branches or pull requests

3 participants