Test plan for "SSH push mirroring support with public-key authentication"
This test plan is for #49565 (closed). The feature allows remote repositories to be updated via SSH push mirroring with public-key authentication.
- Push mirroring, not pull
- Public-key authentication or password
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.
- Respository is
- Mirroring can use public-key authentication.
- When using password authentication the password is obscured (known risk: password is sent as clear text).
- Configuring mirror direction and authentication is simple.
- A key pair is generated automatically and the user can easily copy the public key.
- Mirroring can be initiated on-demand.
- Changes continued to be mirrored as they are made.
Scenario 1: Push mirror using public-key authentication
- Create source and target projects, configure push to target using SSH keys, push.
- Check project exists on target with latest change.
- Make a change to source project. Update mirroring.
- Check target for update.
Scenario 2: Push mirror using password authentication
- As above, but using a password