mirror of
https://github.com/nspcc-dev/neofs-testcases.git
synced 2026-03-01 04:29:19 +00:00
Have case list in text format describing object tests being conducted #344
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#344
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 @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
.pyfile and integrate the codeDescribe 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:
(*) 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