Error messages in lock tests are not descriptive #275

Open
opened 2025-12-28 18:15:36 +00:00 by sami · 1 comment
Owner

Originally created by @carpawell on GitHub (Mar 27, 2024).

tests.object.test_object_lock.TestObjectLockWithGrpc#test_expired_object_should_be_deleted_after_locks_are_expired tests.

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/

Originally created by @carpawell on GitHub (Mar 27, 2024). <!-- Provide a general summary of the issue in the Title above --> `tests.object.test_object_lock.TestObjectLockWithGrpc#test_expired_object_should_be_deleted_after_locks_are_expired` tests. ## Current Behavior Got `Failed: DID NOT RAISE &lt;class 'Exception'&gt;` 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/
Author
Owner

@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?

@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?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-testcases#275
No description provided.