Test plan for "SSH push mirroring support with public-key authentication"

Test Plan

Introduction

This test plan is for https://gitlab.com/gitlab-org/gitlab-ce/issues/49565. The feature allows remote repositories to be updated via SSH push mirroring with public-key authentication.

Scope

  • Push mirroring, not pull
  • Public-key authentication or password

ACC Matrix

Secure Responsive Intuitive Reliable
Repository

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.

Capabilities

  • Respository is
    • Secure
      • Mirroring can use public-key authentication.
      • When using password authentication the password is obscured (known risk: password is sent as clear text).
    • Intuitive
      • Configuring mirror direction and authentication is simple.
      • A key pair is generated automatically and the user can easily copy the public key.
    • Responsive
      • Mirroring can be initiated on-demand.
    • Reliable
      • Changes continued to be mirrored as they are made.

Test Plan

End-to-end tests:

Scenario 1: Push mirror using public-key authentication

  1. Launch a target GitLab instance.
  2. Launch a source GitLab instance, create a project, configure push to target using SSH keys, push.
  3. Check project exists on target with latest change.
  4. Make a change to source project. Update mirroring.
  5. Check target for update.

Scenario 2: Push mirror using password authentication

  1. As above, but using a password

Test Coverage sheet

Assignee Loading
Time tracking Loading