bcgov / bcgov/entity

Create coordinated test strategy

Open
#9,855 2 comments 0 reactions 2 assignees Claimed by @riyazuddinsyed View on GitHub
ENTITY - DO NOT USE Epic techdebt
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

## Current Issues:
- in our releases, some issues would have been caught earlier if we had had more fulcome testing
- QA unable to do fullsome regression testing as not enough automation
- current Test DB has incomplete data for entities

## Ideas:
create data set
create set of tests (known starting points and the test) at the story or epic level
Use data set and tests across environments (DEV/TEST/PROD)
we could E2E tests in PROD

## Business Value:
- removed current testing blockers due to data corruption
- would develop an automated suite of testing
- reduce manual testing effort
- more fullsome verification and regression testing

## Approach for tests:
- Pick a filing
- Sit with Sienna to brainstorm scenarios
- Review scenarios with Linda
- Riyaz to write scripts (if any are missing)
- add suite of tests to pipeline

## Approach for test data:
This isn't fixing all the data in the current environments, it is creating a set of data needed for the test suite.
- Could use standard BCOL account
- Credit card series? could be issue for audit purposes
- hide from users?
have their own sequencing for numbers so obviously different from real-life productions.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.