-
Notifications
You must be signed in to change notification settings - Fork 0
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
test: add integration test scenarios [PAGOPA-1630] #23
Conversation
integration-test/src/features/concatenate-CRUD-by-file-upload.feature
Outdated
Show resolved
Hide resolved
integration-test/src/features/concatenate-CRUD-by-file-upload.feature
Outdated
Show resolved
Hide resolved
integration-test/src/features/concatenate-CRUD-by-file-upload.feature
Outdated
Show resolved
Hide resolved
Scenario: Create, Update and Delete same Debt Position by file upload OK | ||
// todo | ||
|
||
Scenario: N x Create same Debt Position by file upload OK |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
N x
stands for ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
N
creation by file upload: i.e. N
files containing debt positions are being created and the files are submitted via POST N
times
it is not very clear I will write it better
Then check statusCode is 202 | ||
And check location header regex ^brokers/(.+)/organizations/(.+)/debtpositions/file/(.+)/status$ | ||
|
||
Scenario: Create Debt Position by file upload KO: invalid zip |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
invalid zip
== ???
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a zip containing more than 1 file or a file not in JSON format is invalid. Could I split these two cases, making the cases explicit?
Background: | ||
Given GPD-Upload running | ||
|
||
Scenario: Create Debt Position by file upload KO: file size > limit size |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add limit size (xxxMb)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The effective size, greater than the limit, is already in the scenario, one day it could be GB, I prefer maintain scenario description more generic whether you agree
Quality Gate passedIssues Measures |
List of Changes
New integration test scenarios:
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: