[Communication] - Chat - Bug: Fixed chat tests issue token renaming issue #16786
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
jbeauregardb
requested review from
ankitarorabit,
memontic-ms,
turalf and
a team
as code owners
ghost
added
the
jbeauregardb
force-pushed
the
chat_renaming_fix
branch
from
286d1a1
to
637e9e3
Compare
jbeauregardb
force-pushed
the
chat_renaming_fix
branch
from
637e9e3
to
3539054
Compare
|
Looks good, could u also run the live tests? |
|
/azp run python - communication - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Do you need to run the E2E tests there were mentioned in the thread in the Chat team channel? |
RezaJooyandeh
approved these changes
Feb 17, 2021
minnieliu
approved these changes
Feb 17, 2021
lsundaralingam
approved these changes
Feb 17, 2021
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.
No description provided.