Skip to content
This repository has been archived by the owner on Jun 4, 2024. It is now read-only.

Latest commit

 

History

History
101 lines (70 loc) · 3.9 KB

testplan.md

File metadata and controls

101 lines (70 loc) · 3.9 KB
Raw

Manual Testing Plan

Below are the items that should be manually tested with each release of Teleport Plugins. These tests should be run on both a fresh install of the version to be released as well as an upgrade of the previous version of Teleport Plugin.

This test plan is based on Teleport's, it should be run on plugin release and with each new Teleport Release.

General Plugin Setup

  • Able to export auth creds from Teleport. $ tctl auth sign --format=tls --user=access-plugin --out=auth --ttl=8760h
  • Able to create a user and role for access.

Slack Plugin

  • Creating Slack Plugin and OAuth token instructions are up-to-date.

  • teleport-slack configure outputs valid TOML

  • Plugin started with TLS

  • Plugin started --insecure-no-tls

  • End user's tsh login --request-roles=REQUESTED_ROLE appears in Slack

  • Any Slack user in specific room is able to Approve the request.

  • End user now sees role approved in CLI

  • Any Slack user in specific room is able to Deny the request.

  • End user now sees role denied in CLI

  • A long running request should gracefully degrade

  • Teleport Audit log displays correct user approve/deny in UI ( /audit/events )

Mattermost Plugin

  • Creating Mattermost Plugin and OAuth token instructions are up-to-date.

  • teleport-mattermost configure outputs valid TOML

  • Plugin started with TLS

  • Plugin started --insecure-no-tls

  • End user's tsh login --request-roles=REQUESTED_ROLE appears in Mattermost

  • Any Mattermost users in specific room is able to Approve the request.

  • End user now sees role approved in CLI

  • Any Mattermost users in specific room is able to Deny the request.

  • End user now sees role denied in CLI

  • A long running request should gracefully degrade

  • Teleport Audit log displays correct user approve/deny in UI ( /audit/events )

Pagerduty Plugin

  • Creating PagerDuty Plugin and OAuth token instructions are up-to-date.

  • teleport-pagerduty configure outputs valid TOML

  • Plugin started with TLS

  • Plugin started --insecure-no-tls

  • End user's tsh login --request-roles=REQUESTED_ROLE appears in PagerDuty

  • Any PagerDuty on call is able to approve the request.

  • End user now sees role approved in CLI

  • Any PagerDuty on call is able to deny the request.

  • End user now sees role denied in CLI

  • A long running request should gracefully degrade

  • Teleport Audit log displays correct user approve/deny in UI ( /audit/events )

Jira Cloud Plugin

  • Setting up Jira Board and OAuth token instructions are up-to-date.

  • teleport-jira configure outputs valid TOML

  • Plugin started with TLS

  • Plugin started --insecure-no-tls

  • End user's tsh login --request-roles=REQUESTED_ROLE appears in Jira Board

  • Any Jira board member is able to Approve the request.

  • End user now sees role approved in CLI

  • Any Jira board member is able to Deny the request.

  • End user now sees role denied in CLI

  • A long running request should gracefully degrade

  • Teleport Audit log displays correct user approve/deny in UI ( /audit/events )

Jira Server Plugin

  • Setup has been configured using Jira Server 8+

  • Setting up Jira Board and OAuth token instructions are up-to-date.

  • teleport-jira configure outputs valid TOML

  • Plugin started with TLS

  • Plugin started --insecure-no-tls

  • End user's tsh login --request-roles=REQUESTED_ROLE appears in Jira Board

  • Any Jira board member is able to Approve the request.

  • End user now sees role approved in CLI

  • Any Jira board member is able to Deny the request.

  • End user now sees role denied in CLI

  • A long running request should gracefully degrade

  • Teleport Audit log displays correct user approve/deny in UI ( /audit/events )