Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • stackspin stackspin
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 151
    • Issues 151
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • stackspinstackspin
  • stackspinstackspin
  • Issues
  • #1307
Closed
Open
Issue created Jun 16, 2022 by Arie Peterson@arieOwner

Remove nextcloud taiko tests from Stackspin repo

We currently have nextcloud taiko tests in two places:

  1. in the nextcloud repo, run by helm test as part of that repo's CI;
  2. in the stackspin repo, as we have it for other apps.

Basically 2. is still lingering even though we moved the tests to 1. To prevent all kinds of confusion and double work, we should really remove the nextcloud taiko tests from stackspin, and run them in the stackspin CI via helm test instead.

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