Error messages in lock tests are not descriptive

[carpawell]

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/

[carpawell]

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?