[Review Changes] Issue-WV2597 CommentsOut all the Twitter SignIn commands(Regression run failure fixes for SignInpage)#4844
Open
AnujaLawankar wants to merge 1 commit into
Conversation
…ands(Regression run failure fixes for SignInpage)
charanya-QA
suggested changes
Jun 23, 2026
charanya-QA
left a comment
Contributor
There was a problem hiding this comment.
@AnujaLawankar : Can you please explain the new files that have been added? Also , could you please share the browserstack link of the test cases passing with these changes? Thanks!
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
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.
[Review Changes] Issue-WV2597 CommentsOut all the Twitter SignIn commands(Regression run failure fixes for SignInpage)
What github.com/wevote/WebApp/issues does this fix?
I commented all the code for twitter SignIn for Regression testing of SignIn Page.
Changes included this pull request?
Yes, All the changes are in signedin.browser.js and FAQPage.browser.js