Skip to content

v1.1.1

Choose a tag to compare

@github-actions github-actions released this 15 Oct 14:47
· 51 commits to main since this release

This release finishes the drop onto Explorer that 1.1.0 started, gives a click its other buttons, and
closes a gap a reader of the 374-to-352 article measured in the claim diff. Three changes add new
format. One refuses a case file that loaded before, and it is marked may notice.

A step can read a file on disk

1.1.0 let a drag drop a file onto an Explorer folder, and left checking that it arrived to "the next
step", which no step could do: a file on disk is in no window's tree. A step may now name a file
instead of a locator or a tray icon. It takes read and makes one claim, sameBytesAs:

{ "file": "{files}/landing/report.bin", "act": "read", "sameBytesAs": "cases/fixtures/report.bin" }

Both paths are relative to the project's root or name the fixture's staged directory with {files}.
The step waits over timeouts.resolve, because Explorer writes a dropped file after the release
returns. A file still missing then is a failure naming what the folder holds. One that differs names
both lengths and the first byte that differs. A file step without sameBytesAs is refused, because
a file that merely exists is what a truncated copy is too.

A fixture can open an Explorer folder beside the window

{ "name": "with a landing folder", "files": ["cases/fixtures/report.bin"], "opens": "{files}/landing" }

opens creates the folder and opens it in Explorer before the case starts. The window under test
and the folder go side by side on the primary display, so a drop released over the folder lands in
it, and the desk is handed back to the window under test. The folder's window is closed when the case
gives its window back. One still standing after timeouts.stop is named among the survivors, and
one that never opens makes the case a hole naming the desk. opens beside shareable is refused.

With the two together, a drag onto Explorer and the check that the file landed byte for byte is a
case file, with no C# beside it.

A click can press the middle or the right button

{ "locator": "TabItem#second", "act": "click", "with": "PointerIsTheAct", "button": "middle" }

A middle click closes a tab in every browser and terminal on Windows, and a right click opens a
context menu. click used to press only the left button. button takes left, middle or
right, and defaults to left, so no existing case changes. The step's name in the report says the
button. A name that is not a button is refused with the three there are, and button beside any act
but click is refused.

A catches that only repeats the case's name is refused

(May notice.) 1.1.0's lastRun compares what each case catches from one run to the next, so a
rename that keeps its claim stays quiet. A reader of the 374-to-352 article measured what happens when
the claim is just the case name again: the comparison turns back into a comparison of names, reports
every rename as a lost claim, and misses a case that kept its name and changed what it checks.

A case whose catches equals its own name, ignoring case, spacing and punctuation, is now refused
where it is written. A claim that only contains the name inside a longer sentence is accepted. If a
suite of yours stops loading on this, write what the case catches rather than what it is called.

Full Changelog: v1.1.0...v1.1.1