Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • Autosubmit GUI Autosubmit GUI
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • Autosubmit GUIAutosubmit GUI
  • Issues
  • #93
Closed
Open
Issue created Nov 23, 2023 by Bruno de Paula Kinoshita@bdepaulaOwner

Use e2e tests in the UI

We can run e2e tests that allow us to test things like components being mounted/unmounted, DOM changes, events, and other things that would be difficult to do with just unit tests, karma, qunit, jest, etc.

I used Cypress + offline data in the past. The offline data was served with a json-server and saved JSON data, used both for e2e tests and for quick prototype and development. Maybe we could use something similar.

There are alternatives to Cypress, like Nightwatch and Selenium too.

One thing that blocks this issue right now, I think, is the necessity to have a worker with these tools in GitLab. As far as I recall, our single worker is a VM with a shared Conda environment, used mainly/exclusively for Autosubmit Python. Messing up with that might break the worker and Autosubmit (as I did some months ago).

Assignee
Assign to
Time tracking