summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorFrancesco Borzì <borzifrancesco@gmail.com>2021-12-25 16:33:45 +0100
committerGitHub <noreply@github.com>2021-12-25 16:33:45 +0100
commit368417b330eed2a1f441edddd853f6209f81cffd (patch)
tree8c4fb86261736ded0c6d06773148740c5d95c7a4 /docs
parent16517561115179d392e2397e0c72a91c5128e715 (diff)
downloadwiki-368417b330eed2a1f441edddd853f6209f81cffd.tar.gz
wiki-368417b330eed2a1f441edddd853f6209f81cffd.tar.bz2
wiki-368417b330eed2a1f441edddd853f6209f81cffd.zip
fix(keira3-internals/e2e): replace Spectron with Playwright (#667)
Diffstat (limited to 'docs')
-rw-r--r--docs/keira3-internals.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/keira3-internals.md b/docs/keira3-internals.md
index d080bde..96f11b0 100644
--- a/docs/keira3-internals.md
+++ b/docs/keira3-internals.md
@@ -40,8 +40,8 @@ More specifically, we have:
You can see the integration tests of Keira3 almost like a set of e2e tests, the main difference is that all the DB interactions are mocked.
The difference between unit tests and integration test is: in unit tests we test units by mocking all their dependencies, while in integration tests we test "big pieces" of Keira3 together (mocking only the DB). Mostly used to test the editors.
- - **E2E tests**. We have a tiny set of e2e tests based on [Spectron](https://www.electronjs.org/spectron). For example, to check the sqlite integration.
- The command `ng e2e` will automatically serve the app and run the e2e tests.
+ - **E2E tests**. We have a tiny set of e2e tests based on [Playwright](https://playwright.dev/). For example, to check the sqlite integration.
+ The command `npm run e2e` will automatically serve the app and run the e2e tests.
### Why test automation?