E2E tests for riverty #1169
Merged
E2E tests for riverty #1169
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
|
zenit2001
requested review from
amihajlovski,
dcardos,
shanikantsingh,
shubhamk67 and
ShubhamVijaivargiya
as code owners
shubhamk67
approved these changes
Sep 6, 2024
shanikantsingh
approved these changes
Sep 9, 2024
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.
Summary
Describe the changes proposed in this pull request:
Testing Riverty in the pipeline via E2E test.
It adds two e2e tests in the
quickpipeline for riverty. Moreover it adjusts the setEmail() function which is used by the pipeline to accept different emails besides the hardcoded one which we use in most of the test cases.Tested scenarios
Description of tested scenarios:
Fixed issue: SFI-761