NC | lifecycle | Add Tests in POSIX Integration Tests - Part 1

[shirady]

Describe the Problem

We want to expand our test coverage in the NC lifecycle test.

Explain the Changes

1. Create an enum for the status for easier reuse.
2. Fix the description mismatch (id) in the rule lifecycle_rule_delete_all.
3. Rename the file: remove the suffix cli and replace it with posix_integration, also inside the test titles, remove the cli and replace it with nc.
4. Separate with additional describe parts.
5. Remove the test "abort mpu by tags" as according to the docs:

When you use the ExpiredObjectDeleteMarker S3 Lifecycle action, the rule cannot specify a tag-based filter.

Note: We added a validation for this - see issue #8870

7. Add cases where the status is Disabled and the rule doesn't run (in partially picked cases).
8. In versioning:

• DISABLED, add the test cases for nested key and content dir
• ENABLED only for nested key (as content dir is an unsupported case - see our design doc of versioning).
  using Jest feature it.each (see Jest docs - we used array of objects and in the title we used the placeholder of $description to add information in the title).
  Note: The tests were picked (we didn't want to run them on all the existing tests, although we can).

9. Add a warning to the JSDoc function update_file_mtime.
10. Format document.
11. Add the name test in our docs with a short explanation.

Issues:

1. GAPS - we still have more tests that we plan to add to improve our coverage.

Testing Instructions:

Automatic Tests

1. Please run: sudo npx jest test_nc_lifecycle_posix_integration.test

• Doc added/updated
• Tests added

[nadavMiz]

LGTM, minor comment