Skip to content

Conversation

@jonasbardino
Copy link
Contributor

Basic mig/shared/filemarks.py function test coverage reusing the overall structure from the other unit tests.

@jonasbardino jonasbardino self-assigned this Nov 9, 2025
@jonasbardino jonasbardino added the test-only Improvements or additions solely for better test coverage - without functionality changes label Nov 9, 2025
@jonasbardino jonasbardino marked this pull request as ready for review November 9, 2025 18:19
@jonasbardino jonasbardino requested a review from a team November 9, 2025 18:19
@jonasbardino jonasbardino force-pushed the add/mig-shared-filemarks-unit-tests branch from 7708fdc to cbfb08d Compare November 12, 2025 14:13
disabled when run as privileged user like in our doker CI because basic ACLs
are not fully enforced in that case.
@jonasbardino jonasbardino force-pushed the add/mig-shared-filemarks-unit-tests branch from cbfb08d to 7d1d88e Compare December 17, 2025 17:53
reset_result = reset_filemark(self.configuration, self.marks_base,
[TEST_MARKS_FILE], delete=True)
self.assertTrue(reset_result)
retrieved = get_filemark(self.configuration, self.marks_base,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not entirely clear which parts of this are arranging the test "situation" and which part is act.

Copy link
Contributor

@albu-diku albu-diku left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This test is relatively strightforward. I have noted that in at least one of the tests it isn't clear which of the operations correspnding to arranging the test cirsumstances and what is the operation that is actually being checked (act), which could use some clarification.

This also has the test name and docstring duplication, as mentioned #390 (comment). It affect that pull request much more than this one, and ideally we would address that before it goes in-tree. It looks like the docstrings in this file contain a more direct description of what is being tested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test-only Improvements or additions solely for better test coverage - without functionality changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants