574 category and credential e2e tests #626
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mikeplotean
force-pushed
the
574-category-and-credential-e2e-tests
branch
2 times, most recently
from
ccb97ce
to
f8b2dc4
Compare
mikeplotean
force-pushed
the
574-category-and-credential-e2e-tests
branch
2 times, most recently
from
654dd5e
to
d687b36
Compare
waltkb
approved these changes
Jul 18, 2024
mikeplotean
force-pushed
the
574-category-and-credential-e2e-tests
branch
from
d687b36
to
bc37190
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds api tests for category, credentials and exchange wallet endpoints. Fixes a cli test related to illegal path character on Windows.
Fixes #574
Type of Change
New feature (non-breaking change which adds functionality)Breaking change (fix or feature that would cause existing functionality to not work as expected)This change requires a documentation updateChecklist
If it is a core feature, I have added thorough testsDo we need to implement analytics?Will this be part of a product update? If yes, please write one phrase about this update.I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationMy changes generate no new warnings