Test Plan for "New user flow for SSOing into a GitLab.com group"

Test Plan

Introduction

This test plan is for https://gitlab.com/gitlab-org/gitlab-ee/issues/5292. This feature introduces a new user login and registration flow that allows creating a user and linking it to the Group when user tries to access an SSO enabled group.

Scope

  • Includes creating a new user as part of the SAML SSO group login flow
  • Does not include forcing a user to use dedicated credentials for a group which is a separate issue

ACC Matrix

The matrix below identifies the Attributes, Components, and Capabilities relevant to the scope of this test plan.

Attributes (columns) are adverbs or adjectives that describe (at a high level) the qualities testing is meant to ensure Components have.

Components (rows) are nouns that define major parts of the product being tested.

Capabilities link Attributes and Components. They are what your product needs to do to make sure a Component fulfils an Attribute

This feature includes "Projects" and "Groups" functional area and so they included in the matrix.

For more information see the Google Testing Blog article about the 10 minute test plan and this wiki page from an open-source tool that implements the ACC model.

The numbers indicate the count of Capabilities at each intersection of Attribute and Component

Secure Responsive Intuitive Reliable
Groups 1 4

Capabilities

  • Groups (SAML SSO Login/Registration) is
    • Intuitive
      • It is easy for the user to login with an existing linked account or create a new account
    • Reliable
      • Registration creates an SAML identity link between user and group correctly.
      • Already signed in user with no existing identity link is signed out and presented with registration page
      • Already signed in user with an existing identity link is signed in to the group.
      • Email address is provided by the idp and the user should not be able to change it on the registration form.

Test Plan

The scope of this feature is small enough that a list of tests is not required. It is enough to use the Capabilities to guide your testing.