Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • S Schema
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Schema
  • Merge requests
  • !92

Adding multi tenancy tests

  • Review changes

  • Download
  • Patches
  • Plain diff
Closed Ashay Bansod requested to merge addingMultiTenancyTests into master Mar 09, 2021
  • Overview 1
  • Commits 7
  • Pipelines 6
  • Changes 8

Adding multi-tenancy test cases to schema service integration tests. These are not to run in gitlab using tag feature as only single tenant infra is available. When ever any consumer would have infra to execute this, it will have to run specific tag 'NotToRunInGitlab' along with 'SchemaService' tag. Removed pre and post integration file (runner, step-def along with pom changes) as they are not configured for schema service anyways. Setup part of schema service is being already handled using background feature of BDD. So, no impact of current integration setup.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: addingMultiTenancyTests