Test Plan for "Create a user via SCIM"
Test Plan
Introduction
This is a test plan for https://gitlab.com/gitlab-org/gitlab-ee/issues/9201
The issue is for implementing limited SCIM 2.0 API endpoints that would allow automatic provisioning/creating of users by an identity provider.
Also see: Test Plan for "Automatically deprovision users when removed from a configured identity provider"
Scope
- Includes
POST /groups/:group/users
endpoint - Does not include any other endpoints from the SCIM protocol specification
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 the "API" and so it is 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 | |
---|---|---|---|---|
API | 1 | 1 | 2 |
Capabilities
- API is
- Secure
- It is only accessible with a valid SCIM Access token (or Personal Access Token until SCIM Access token is implemented)
- Intuitive
- It follows the SCIM Protocol Specification (RFC 7644)
- Reliable
-
POST /groups/:group/users
correctly creates the user in the provided:group
- After creation, response of
GET /groups/:group/users
includes the created user
-
- Secure