CodeDeploy Config - Appspec file + scripts #23
Conversation
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
Muukreport on mkcli to internal_executor
Aboout line: expectedValue.endswith(element['src'][2:None]))
Domparser validations s98
…tests Insights are not showed on successful tests
adding faker library
Get browser stack video
Executor on ubuntu 2024 and using webdriver manager
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.
Brief summary of the problem and the fix.
Configuration required for the codeDeploy revision.
Added Appspec file and scripts.
Task or/and github covered by this fix
Prototype#1259
Tests executed
E2E
Answer the following questions:
Does the PR have any dependency with BE or FE? If so, specify which PR
No
In case of a dependency, could you describe what would happen if not delivered together? (eg. FE will crash, code will not compile, etc)
None
Did you add a new lib package (package.json)? If so, did you update the open source spreadsheet?
No
Did you link the defect to this PR (Github only)
Not possible
If you are adding a new FE view or any significant UI change, have you shared the new UI to the team already?
No
Did you include or update the unit tests?
No
Did you execute the npm tests ?
No
Did you test it in both environments (dev/prod)?
No
if you update the routes... Did you update the sample.txt ?
No