mirror of
https://github.com/nspcc-dev/neofs-testcases.git
synced 2026-03-01 04:29:19 +00:00
Error messages in lock tests are not descriptive #275
Labels
No labels
I1
I2
I3
I4
S0
S1
S1
S2
S3
S4
U0
U0
U1
U2
U3
U4
blocked
bug
dependencies
discussion
documentation
enhancement
enhancement
enhancement
epic
feature
good first issue
help wanted
performance
question
task
test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-testcases#275
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @carpawell on GitHub (Mar 27, 2024).
tests.object.test_object_lock.TestObjectLockWithGrpc#test_expired_object_should_be_deleted_after_locks_are_expiredtests.Current Behavior
Got
Failed: DID NOT RAISE <class 'Exception'>message if an object is not deleted.Expected Behavior
Some understandable message about object not deleted after some time.
Possible Solution
Do some assert with a message. It is possible in pytest?
Steps to Reproduce
See https://rest.fs.neo.org/HXSaMJXk2g8C14ht8HSi7BBaiYZ1HeWh2xnWPGQCg4H6/1441-1711487340/index.html#suites/295ed2e000f8fa6f3ade59cc13b98615/3f2b8cbfd27db081/
@carpawell commented on GitHub (Mar 27, 2024):
To be honest, I see SO MANY strange messages in reports so I am dreaming of creating a single issue "check all the error messages" but almost sure it will be rejected. But just imagine me creating 50 issues and writing 50 issue descriptions, will it be really effective?