fix: [#4414] JS Linux Functional Test pipeline failing #4419
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
Pull Request Test Coverage Report for Build 4014919253
💛 - Coveralls |
tracyboehrer
approved these changes
Jan 31, 2023
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.
Fixes #4414
Description
This PR fixes the errors in the JS Linux Functional Test pipeline. It also applies some prettier fixes to the DirectLine tests.
The error
TypeError: Cannot read property 'text' of undefinedwas fixed by upgrading the botSku from F0 to S1, as the bot was throwing an error related to the max transactions being exceeded.We also had an authorization issue that was solved by upgrading the bot's Node version from 10 to 16.
Specific Changes
functionaltestbot/template/linux/template.jsonto upgrade the Node version to 16 and the botSku default value to S1.testing/functional/tests/directLine.test.js.Testing
This image shows the testing pipeline successfully executed after the changes:
