feature: WEOS-1133 Generate and Ensure BDD Test #58
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
- Generated bdd test
shaniah868
changed the title
-Fix BDD Test -Added checks for if the items are named differently to check for its alias -Added the service is running step -Removed the seqno and entityid from feature file -Removed the table_alias from the content entity returned -Change the feature file entityId and sequenceNo to have the same numbering as db
-Add back the tag
-Added paramter to api yaml file
-Fixed failing tests after the merge
-Fixed failing tests after the merge
# Conflicts: # controllers/rest/controller_standard.go # controllers/rest/middleware_context.go # controllers/rest/weos_mocks_test.go
-Fixed failing tests after the merge
RandyDeo
approved these changes
Jan 25, 2022
-Change the tag
atoniaw
approved these changes
Jan 25, 2022
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: