Have case list in text format describing object tests being conducted #344

Open
opened 2025-12-28 18:16:00 +00:00 by sami · 0 comments
Owner

Originally created by @cthulhu-rider on GitHub (Feb 22, 2025).

im always frustrated when i need to realize which cases are not covered, which are covered, and whether their expectations are correct. Some NeoFS services can have many possible settings. Object SearchV2 is one of them

currently, to do this, i need to go to a specific .py file and integrate the code

Describe the solution you'd like

have a text file with list of tests. Refer test funcs in code to them

for example, for SearchV2, each item describes:

  1. what data is prestored
  2. what is being requested
  3. what response is expected
  4. CLI cmd to make the request (*)

(*) this will make it easier to understand whether the cmd matches the request, and if so, to reproduce it

Describe alternatives you've considered

write the same info in comments to test functions in source code. Will still require to surf .py files, but better than nothing

Additional context

Originally created by @cthulhu-rider on GitHub (Feb 22, 2025). ## Is your feature request related to a problem? Please describe. im always frustrated when i need to realize which cases are not covered, which are covered, and whether their expectations are correct. Some NeoFS services can have many possible settings. Object SearchV2 is one of them currently, to do this, i need to go to a specific `.py` file and integrate the code ## Describe the solution you'd like have a text file with list of tests. Refer test funcs in code to them for example, for SearchV2, each item describes: 1. what data is prestored 2. what is being requested 3. what response is expected 4. CLI cmd to make the request (*) (*) this will make it easier to understand whether the cmd matches the request, and if so, to reproduce it ## Describe alternatives you've considered write the same info in comments to test functions in source code. Will still require to surf .py files, but better than nothing ## Additional context * #953
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#344
No description provided.