Check for certain errors not any #119

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

Originally created by @EliChin on GitHub (Jul 8, 2022).

Some operations may fail due to a number of reasons. We should check if failure occurs after a particular expected error. Now we only check if an operation fails regardless of the reason.
First, we need to recognize return codes. See them in types.proto
Second, we need to check CLI return codes, which are the following:

  • 0 -- OK
  • 2 -- ACCESS_DENIED
  • 1 others

Error tracking may be discussed and made more convenient for further testing.

Originally created by @EliChin on GitHub (Jul 8, 2022). Some operations may fail due to a number of reasons. We should check if failure occurs after a **particular expected error**. Now we only check if an operation fails regardless of the reason. First, we need to recognize return codes. See them in [types.proto](https://github.com/nspcc-dev/neofs-api/blob/master/status/types.proto) Second, we need to check CLI return codes, which are the following: - 0 -- OK - 2 -- ACCESS_DENIED - 1 others Error tracking may be discussed and made more convenient for further testing.
Author
Owner

@roman-khimov commented on GitHub (Feb 10, 2025):

Needs correct CLI error codes.

@roman-khimov commented on GitHub (Feb 10, 2025): Needs correct CLI error codes.
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#119
No description provided.