Feature/mc 9691 Verify that default profile fields can be viewed and modified#11
Open
Feature/mc 9691 Verify that default profile fields can be viewed and modified#11
Conversation
e.g. Descriptions, aliases etc
* Also install faker library to generate random string data for text entry
…ofile fields edited
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Default profile fields are things like Description, Organisation, Author, Aliases, etc.
Test scenarios added to check that:
Note: Tests currently assume that the seeded database has some folder/models already marked as "public". This could be an automated step as well to set this up, but its one more thing to slow the tests down.
Requires new DOM selector IDs to be present, which were added in MauroDataMapper/mdm-ui#335