Skip to content
This repository has been archived by the owner on Feb 16, 2025. It is now read-only.

Decision: use manual testing for auth #375

Open
ace-n opened this issue May 10, 2022 · 0 comments
Open

Decision: use manual testing for auth #375

ace-n opened this issue May 10, 2022 · 0 comments
Assignees
@ace-n
Labels
documentation Improvements or additions to documentation needs decision record This issue or change is significant and we should create a decision record. needs docs priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@ace-n
Copy link
Contributor

ace-n commented May 10, 2022

@grayside @engelke and myself agreed upon using manual testing for our Google Account auth flow.

We need to document that decision, and why we chose to do it that way. (TL;DR: some manual testing is fine, and automated testing here is hacky at best.)

cc @pattishin as FYI
@ace-n ace-n added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. needs decision record This issue or change is significant and we should create a decision record. needs docs labels May 10, 2022
@ace-n ace-n self-assigned this May 10, 2022
@ace-n ace-n added type: docs Improvement to the documentation for an API. and removed type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Aug 25, 2022
@ace-n ace-n added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Nov 14, 2022
@grayside grayside added documentation Improvements or additions to documentation and removed type: docs Improvement to the documentation for an API. labels Feb 28, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ace-n ace-n

Labels
documentation Improvements or additions to documentation needs decision record This issue or change is significant and we should create a decision record. needs docs priority: p2 Moderately-important priority. Fix may not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grayside @ace-n