Skip to end of banner
Go to start of banner

2021-04-07 Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Date

04-07-2021

Attendees


Discussion items

Time

Item

Who

Notes

5 minWelcome Mark DeutschTCMark Deutsch will be taking Mike Gorrell's spot on the TC
45 minExpectations for Testing itemsAnton

Create a unified list of expectations relative to testing items that should be part of Definition of Done (note Anton Emelianov (Deactivated)is preparing a recommendation to be reviewed on 2021-03-31)


Anton presented a slide deck. Our current process is that development is done in a scratch environment; Story acceptance is done within a reference environment; manual testing is done within the bugfest testing. This results in 1 regression run every 3-4 months.


Proposed process: Manual test cases get created along with the story, with manual testing done on the scratch environment. Backend and front end unit tests, and karate/postman tests, UI Smoke Test, Cover Test Debt TCs with Automation will all be done within the scratch environment. These things will be done prior to merging a PR.

After the merger of the PR, within the reference environment, performance test, automated UI smoke test, karate and postman regression suites will be run.

Within bugfest additional manual testing and bug fixes will take place.

TC discussed the proposal:

Craig asked if the code smell, bugs and vulnerabilities should be considered in the DoD. Zack preferred that these be surfaced as warnings and not a blocker for merging PRs. 

MarkD asked what we are trying to accomplish through the use of automated tools. Anton says we are trying to establish consistency in the project's coding culture.

Anton clarified his suggestion that manual testing is done via QAs during the initial development phase. Product owners are currently doing much of this QA work. 


0 minSet the stage for Spring Way discussionTC

Status of Spring Way (can leverage this discussion to determine the process for approving new technology)

This discussion was cut for time.

5 minVolunteers for Future TC MeetingsTC




  • No labels