Divide test_expiration_epoch_in_http into several (parametrized) #24
No reviewers
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-testcases#24
Loading…
Reference in a new issue
No description provided.
Delete branch "EliChin/frostfs-testcases:feature/http_4"
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?
Divide test_expiration_epoch_in_http into 2 tests (parametrized)
Signed-off-by: Liza e.chichindaeva@yadro.com
@ -199,3 +199,4 @@
)
@pytest.mark.parametrize("epoch_gap", [0, 1])
@allure.title("Test Expiration-Epoch in HTTP header")
It's better to keep allure.title at the top.
@ -222,3 +223,2 @@
with allure.step("Put objects using HTTP with attribute Expiration-Epoch"):
oids.append(
upload_via_http_gate(
if get_epoch(self.shell, self.cluster) + 1 <= valid_until:
Seems that both if and else have the same steps.
So we shouldn't duplicate it :)
Almost. But
if
adds to the list with oids to stay valid, whileelse
adds to the list of oids to be expired.16eb5e85dd
to184ba91a98
184ba91a98
to78172cb999
78172cb999
to4838f01393
4838f01393
to1e6d3e77f9