Skip to content

Improve e2e testing as part of the local-setup tests #1212

@nexus49

Description

@nexus49

Implement the following improvements

  • Open the link of an HTTPBin and see it working
  • Create a bin in the default namespace
  • Create a new namespace called test using the namespaces view
  • Create a bin the test namespace
  • Use the Namespace dropdown to filter for a particular namespace
  • Try to use the downloaded OIDC kubeconfig to create/modify a resource

Authorization Tests

  • login with a second users (possibly one that was invited before by the first user)
  • validate that the user sees the not authorized page when navigating to an account the first user had created
  • possibly navigate to an account that the first user has created, but where the second user was added as a member of
  • Attempt to manage users and expect to fail (or expect buttons to be hidden/disabled)

Add a cli based test script

  • Test the status of several backend resources:
    • Ready condition of all content Configurations in platform-mesh-system
    • Ready condition of all content Configurations for the httpbin-provider
    • Ready Condition for the Store resource in root:rogs
    • Ready Condition for identityproviderconfiguration in root:orgs:
    • Ready Condition for all WorkspaceTypes in root and root:orgs

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions