Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.editor beat.editor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beat
  • beat.editorbeat.editor
  • Issues
  • #164
Closed
Open
Created Oct 15, 2018 by André Anjos@andre.anjos💬Owner

What does browser-tests stage in the CI do?

I was making changes to BEAT packages regarding their test-only phases. When running in test-only mode, we should not try to build the manual or check the package components anymore, as that will not fly with the current test strategy.

I made modifications to beat.cmdline and beat.core to take this into account (check latest MRs on those packages), simply making sure that sphinx and conda based test lines are only executed during the build and not in test-only phases.

I wanted to do the same for this package, but I wonder what the stage browser-tests really do. It seems to be not doing more than what is done during build.

Could @flavio.tarsetti clarify, please?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking