bcgov / bcgov/STRR

STRR - UAT Decommissioning and Sandbox Enhancement

Open
#1,741 0 comments 0 reactions 0 assignees View on GitHub
STR
Dominant language
Python
Stars
2
Forks
22
Avg merge
2d 35m
Merged PRs (30d)
11

Description

As the product transitions into maintenance mode, the volume and complexity of changes requiring formal User Acceptance Testing are expected to decrease. Maintaining a dedicated UAT environment may no longer be cost-effective. Consolidating UAT activities into the Sandbox environment would reduce operational overhead, simplify environment management, improve resource utilization, and allow the team to focus on enhancing shared testing capabilities and test data management processes.

Before making any decisions regarding environment consolidation or the decommissioning of UAT, we need to conduct a requirements-gathering exercise with all groups that currently use non-production environments.

The objective is to understand how each group uses the environments today, their testing needs, data requirements, access requirements, and any dependencies on existing UAT capabilities. Stakeholders may include Help Desk, API consumers, internal business users, and other support teams.

The information gathered will help determine whether the Sandbox environment can adequately support all required activities, identify any gaps that need to be addressed, and define the capabilities, processes, and Test Data Management solutions required before consolidating environments (refer to https://app.zenhub.com/workspaces/strr-65b2a7146835aa0cdf315b79/issues/gh/bcgov/strr/1467)

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start with the requirements-gathering exercise across Help Desk, API consumers, internal business users, and support teams, documenting environment use, testing, data, access, and dependencies. Done means the requirements, Sandbox gaps, and required capabilities, processes, and test-data management solutions are documented for a consolidation decision.

Written by the indexing model from the issue text.

Assessment

Domain
infrastructure, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.