Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cypress test to upload files #1839

Open
BCerki opened this issue Aug 4, 2023 · 0 comments
Open

Cypress test to upload files #1839

BCerki opened this issue Aug 4, 2023 · 0 comments
Labels
Tech Debt Technical Debt

Comments

@BCerki
Copy link
Collaborator

BCerki commented Aug 4, 2023

###Description of the Tech Debt###

Uploading and deleting files in cypress requires google authentication. We tried to get it working in #1825 and were unsuccessful.

In the cypress test add the assertions:

cy.fixture("e2e/mock.pdf").as("mockFile");
cy.get("input[type=file]").selectFile("@mockFile");

delete them at the end (see the linked PR)

add the google auth action

###Tech Debt Triage#
The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.

Risk Value Scoring:

Level Value
High 3
Medium 2
Low 1
Technical Debt - Risk Types Level Value
Business Area Risk - Risk of business area visibility / damage to user experience
Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it
System Fault Risk - Risk of system errors or application downtime
Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?
Time Sink Risk - How much will this tech debt slow the development process down
TOTAL SCORE:
@BCerki BCerki added the Tech Debt Technical Debt label Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tech Debt Technical Debt
Projects
None yet
Development

No branches or pull requests

1 participant