Playwright integration tests for Forgejo
Go to file
Aravinth Manivannan 28cfa742f2
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
feat: test sign out and sign in
2024-01-10 03:01:10 +05:30
.github/workflows feat: init and add tests for user registration 2024-01-09 23:31:52 +05:30
.reuse feat: add license details 2024-01-09 23:35:51 +05:30
LICENSES feat: add license details 2024-01-09 23:35:51 +05:30
tests feat: test sign out and sign in 2024-01-10 03:01:10 +05:30
tests-examples feat: init and add tests for user registration 2024-01-09 23:31:52 +05:30
.env feat: init and add tests for user registration 2024-01-09 23:31:52 +05:30
.gitignore feat: init and add tests for user registration 2024-01-09 23:31:52 +05:30
.nvmrc feat: init and add tests for user registration 2024-01-09 23:31:52 +05:30
.woodpecker.yml feat: CI: use pre-built base img 2024-01-10 02:25:29 +05:30
docker-compose.yml feat: add docker-compose for local dev env 2024-01-10 02:06:40 +05:30
Dockerfile feat: build CI base img to speedup exec 2024-01-10 02:25:25 +05:30
package-lock.json feat: init and add tests for user registration 2024-01-09 23:31:52 +05:30
package.json feat: init and add tests for user registration 2024-01-09 23:31:52 +05:30
playwright.config.ts feat: init and add tests for user registration 2024-01-09 23:31:52 +05:30
README.md feat: basic README 2024-01-10 02:08:37 +05:30

status-badge


Playwright based integration testing for Forgejo

Development

Dependencies

  • Node v20.10.0: We use nvm for Node version management. If installed, run nvm use in repo directory
  • Docker compose: for spinning up test environment

Usage

Please install development dependencies. Also consider installing browser drivers (see here). On my development, I test only on Firefox and Chromium, so I run:

npx playwright test --project=firefox \
	&& npx playwright test --project=chromium