t7519-status-fsmonitor: improve comments
The comments for the staging/unstaging test did not accurately describe the scenario being tested. It is not essential that the test files being staged/unstaged appear at the end of the index. All that is required is that the test files are not flagged with CE_FSMONITOR_VALID and have a position in the index greater than the number of entries in the index after unstaging. The comment for this test has been updated to be more accurate with respect to the scenario that's being tested. Signed-off-by: William Baker <William.Baker@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
William Baker committed
Oct 16, 2019 at 19:35 UTC
460782b7be869424ff049350bdcbf151f6beca62
1 file changed
+5
-3
t/t7519-status-fsmonitor.sh
+5
-3
@@ -354,9 +354,11 @@ test_expect_success 'discard_index() also discards fsmonitor info' '
354
test_cmp expect actual
355
'
356
357
-# Test staging/unstaging files that appear at the end of the index. Test
358
-# file names begin with 'z' so that they are sorted to the end of the index.
359
-test_expect_success 'status succeeds after staging/unstaging ' '
357
+# Test unstaging entries that:
358
+# - Are not flagged with CE_FSMONITOR_VALID
359
+# - Have a position in the index >= the number of entries present in the index
360
+# after unstaging.
361
+test_expect_success 'status succeeds after staging/unstaging' '
362
test_create_repo fsmonitor-stage-unstage &&
363
(
364
cd fsmonitor-stage-unstage &&