Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WIP] ADR integration-test with Playwright #3071

Open
wants to merge 1 commit into
base: refactor
Choose a base branch
from
Open

[WIP] ADR integration-test with Playwright #3071

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,6 +79,18 @@ flutter build web
```
or you can find our images in: https://hub.docker.com/r/linagora/tmail-web

## Integration Test
1. Config Java enviroment (Java 22) with Maven
2. Build docker image with name: `tmail-web:integration-test`
```
docker build -t tmail-web:integration-test .
```
3. Test
```
cd tmail_integration_test
mvn test
```

## FAQ

### **Why did you choose JMAP?**
Expand Down
22 changes: 22 additions & 0 deletions docs/adr/0052-web-integration-test-with-playwright
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
# 52. Web integration test with PlayWright

Date: 2024-08-07

## Status

Accepted

## Context

To enhance test coverage and efficiency, we require a robust integration testing solution to mitigate regression risks and minimize manual testing efforts.
Flutter Drive, our current built-in framework, exhibits limitations in handling specific scenarios such as Single Sign-On (SSO) and redirects.
Selenium could be an option, but ... //will add more
Beside that, we can leverage the backend team's Java expertise for a Java-based testing framework.

## Decision

To address these challenges, we will adopt the ROBOT pattern for Playwright and maintain integration test suites within the tmail-flutter project.

## Consequences

To ensure ongoing test effectiveness, we will implement integration tests for all new features to prevent regressions. Additionally, we will prioritize adding integration tests for frequently occurring use cases to bolster overall test coverage.
Loading