aboutsummaryrefslogtreecommitdiff
path: root/cmd/krino/sort_test.go
diff options
context:
space:
mode:
Diffstat (limited to 'cmd/krino/sort_test.go')
-rw-r--r--cmd/krino/sort_test.go48
1 files changed, 24 insertions, 24 deletions
diff --git a/cmd/krino/sort_test.go b/cmd/krino/sort_test.go
index 4f3e29f..4e68cb5 100644
--- a/cmd/krino/sort_test.go
+++ b/cmd/krino/sort_test.go
@@ -31,9 +31,9 @@ func TestRelWidthAndPadCellCountRunes(t *testing.T) {
}
}
-// TestActionableChainsAgreesWithCountActing is fix wave item 4 / Minor 5:
-// countActing (render.go) and actionableChains used to disagree over a
-// chain every one of whose steps is skipped (len(Steps) > 0, but every
+// TestActionableChainsAgreesWithCountActing: countActing (render.go) and
+// actionableChains used to disagree over a chain every one of whose steps
+// is skipped (len(Steps) > 0, but every
// step's own Skip is set) - countActing already excluded it from "to act
// on", while actionableChains's own len(Steps) > 0 check still offered it
// for approval, so a directory could print "N scanned · 0 to act on" and
@@ -53,17 +53,17 @@ func TestActionableChainsAgreesWithCountActing(t *testing.T) {
}
}
-// TestAllSkippedDirectoryReportsZeroAndLogsNothing is fix wave item 4 /
-// Minor 5 and 6, end to end. Before the fix: a directory whose one file
-// matches a rule under (on-conflict skip) - so its single step's own Skip
-// is set ("target exists") - printed "0 to act on" (countActing) and then,
-// with -y, still ran that chain through Apply anyway (actionableChains'
-// own len(Steps) > 0 check approved it regardless), logging a
-// run-start/run-end pair holding only a "skipped" entry while the outcome
-// line read "0 applied · 0 failed · 0 declined" for a file that had just
-// been silently processed. After the fix, the chain is never offered for
-// approval, Apply is never even called for this directory, and the journal
-// gains nothing at all.
+// TestAllSkippedDirectoryReportsZeroAndLogsNothing, end to end: a
+// directory whose one file matches a rule under (on-conflict skip) - so
+// its single step's own Skip is set ("target exists") - must report "0 to
+// act on" (countActing) and, with -y, must not run that chain through
+// Apply anyway: an all-skipped chain offered for approval regardless
+// (as actionableChains' own len(Steps) > 0 check alone would allow) would
+// log a run-start/run-end pair holding only a "skipped" entry while the
+// outcome line read "0 applied · 0 failed · 0 declined" for a file that
+// had just been silently processed. Instead the chain is never offered
+// for approval, Apply is never even called for this directory, and the
+// journal gains nothing at all.
func TestAllSkippedDirectoryReportsZeroAndLogsNothing(t *testing.T) {
h := home(t)
dl := filepath.Join(h, "dl")
@@ -225,7 +225,7 @@ func TestDryRunShowsNeverDeletedSkip(t *testing.T) {
if !strings.Contains(out, "skipped: a duplicate is never deleted") {
t.Errorf("plan lacks the skipped delete:\n%s", out)
}
- // explain shows it too, for the copy that is the duplicate (triage 30a).
+ // explain shows it too, for the copy that is the duplicate.
_, outA, _ := runCLI(t, "explain", filepath.Join(dl, "a.pdf"))
_, outB, _ := runCLI(t, "explain", filepath.Join(dl, "b.pdf"))
if strings.Count(outA+outB, "a duplicate is never deleted") != 1 {
@@ -235,8 +235,8 @@ func TestDryRunShowsNeverDeletedSkip(t *testing.T) {
// TestLaterDirectoryIsNotBlockedByAnEarlierOnesClaims: in a real run each
// directory is applied before the next is planned, so the disk is the
-// truth; a path an earlier directory moved a file away from, or planned and
-// did not apply, is not "taken" for a later one (triage 28i).
+// truth; a path an earlier directory moved a file away from, or planned
+// and did not apply, is not "taken" for a later one.
func TestLaterDirectoryIsNotBlockedByAnEarlierOnesClaims(t *testing.T) {
h := home(t)
old := time.Date(2026, 1, 1, 0, 0, 0, 0, time.UTC)
@@ -300,8 +300,8 @@ func devFullFixture(t *testing.T) {
}
// TestApplyErrorExitsOne: an error applying a directory - here the log
-// cannot be written - makes krino exit 1 (triage 34m: removing that exit
-// code left every test passing).
+// cannot be written - makes krino exit 1; removing that exit code left
+// every other test passing.
func TestApplyErrorExitsOne(t *testing.T) {
devFullFixture(t)
code, _, errOut := runCLI(t, "-y", "d1")
@@ -311,9 +311,9 @@ func TestApplyErrorExitsOne(t *testing.T) {
}
// TestWriteStopsKrinoWhenApplyFails: [w] in review stops krino after its
-// directory even when applying it fails - the next directory is not planned
-// or asked about (review cli F3), driven through the real command with a
-// pipe standing in for the terminal (triage 28m).
+// directory even when applying it fails - the next directory is not
+// planned or asked about, driven through the real command with a pipe
+// standing in for the terminal.
func TestWriteStopsKrinoWhenApplyFails(t *testing.T) {
devFullFixture(t)
r, w, err := os.Pipe()
@@ -337,7 +337,7 @@ func TestWriteStopsKrinoWhenApplyFails(t *testing.T) {
// TestLaterDirectoryNeverOverwritesAnEarlierOnesResult: what an earlier
// directory of the run put somewhere stays claimed, so a later directory's
// (on-conflict overwrite) takes a free name instead of trashing it - as a
-// dry run of the same two directories shows (plan 11 review M1).
+// dry run of the same two directories shows.
func TestLaterDirectoryNeverOverwritesAnEarlierOnesResult(t *testing.T) {
h := home(t)
old := time.Date(2026, 1, 1, 0, 0, 0, 0, time.UTC)
@@ -369,7 +369,7 @@ func TestLaterDirectoryNeverOverwritesAnEarlierOnesResult(t *testing.T) {
// TestOnlyWhereFilesEndedUpStaysClaimed: a path an earlier directory's file
// passed through and left - renamed, then moved on - is free for a later
-// directory; only where files ended up stays claimed (plan 11 re-check).
+// directory; only where files ended up stays claimed.
func TestOnlyWhereFilesEndedUpStaysClaimed(t *testing.T) {
h := home(t)
old := time.Date(2026, 1, 1, 0, 0, 0, 0, time.UTC)