After setting up the scaffolding for E2E testing, we can now add some E2E tests for the essential features.

I think we could implement the same tests we have in the backend (or at least a subset):

https://github.com/torrust/torrust-index-backend/tree/develop/tests/e2e/web/api/v1/contexts

IMPORTANT: if you'd like to contribute, you can pick up a test and open a new issue. This issue only keeps track of all the E2E tests pending implementation.

Guest

• Registration
• List torrents
  • With no torrents
  • With pagination
  • With table mode
  • Filtering by category
  • Filtering by tag
  • Searching for words in the torrent title
  • Sorting by newest/oldest
  • Sorting by seeders/leechers
  • E2E tests: generate magnet link (on list page) #232
  • See metadata: title, description, category, tags
  • See the number of leechers/seeders
  • E2E tests: download a torrent #221
  • E2E tests: generate magnet link (on details page) #230

Registered user

• E2E tests: user login #178
• E2E tests: upload a torrent #180
• Edit torrent info/metadata (title, description, category, tags)
• Advanced torrent edition:
  • Use markdown in the torrent description (for example, a bold text).
  • Use proxied images (JPG or PNG).

Admin

Categories

• E2E tests: add a new category #224
• E2E tests: delete a category #226

Tags

• E2E test: add a new tag #228
• E2E test: delete a tag #229

Backend settings

• View backend settings

We can create subtasks for one or multiple E2E tests depending on how hard it is to implement them.

Subtasks

• E2E testing scaffolding #144