Week 2: catir-robcla presentation proposal #2376
Merged
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
javierron
added
proposal
|
@RobinClaesson Thanks for the proposal. |
Merged
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.
Assignment Proposal
Title
Automated UI testing using Playwright
Names and KTH ID
Deadline
Category
Description
We want to give a presentation with an introduction to Playwright. Playwright is an open source framework that enables automated testing for UI of web apps supporting chromium, firefox, and web-kit, and is available for several popular programming languages.
We will first explain why automated UI testing is needed to fill the gaps of regular unit tests. We will then introduce Playwright and show small examples of its usage, including intercepting Api requests and returning expected results.
Relevance
Running unit tests in a CI pipeline is a common practice to ensure the integrity of the software before allowing a merge. Even if every function is extensively tested and works as intended, the web app will still not work if its elements are not correctly mapped to their corresponding functions. Automating UI testing in the CI pipeline together with the unit tests ensures that your web app's components works as intended before deploying to production.