[#338] Automation of PATCH method in S3 #338
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-testcases#338
Loading…
Reference in a new issue
No description provided.
Delete branch "Kiriruso/frostfs-testcases:feature-patch-testsuite-part-two"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Signed-off-by: Kirill Sosnovskikh k.sosnovskikh@yadro.com
b7cde46498
toaf74135546
af74135546
to7184cc511b
@ -0,0 +26,4 @@
PART_SIZE_FOR_MULTIPART = 5 * 1024 * 1024
def pytest_generate_tests(metafunc: pytest.Metafunc) -> None:
can we remove generate_tests from here?
It is possible, but then for all tests using
s3_client
I would have to add parameterization ofs3_policy
, which is not very convenient. I can apply parameterization to the whole class, but not all tests uses3_client
, so it will not work.Add parameterization for tests using
s3_client
?7184cc511b
todc6a136d6b
dc6a136d6b
toa2567c2643
a2567c2643
tofb9b75ce39
fb9b75ce39
to31c4b3eb02
31c4b3eb02
toe0319a7b4b
e0319a7b4b
toa1f7848262
a1f7848262
toed2b885c03
ed2b885c03
toa5fcd03a9d