| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
This takes away the need for multi-level escaping in scenario setup.
Post-conditions like screen-should-contain are still an issue, though.
Maybe each string literal should be able to specify escapes inside its
syntax? Or at a per-instruction granularity?
|
| |
|
|
|
|
| |
I still want to bring back replace-in-keyboard. No, not exactly that.
But saying press 8, press 8, press 8, over and over again, that's a
pain.
|
| |
|
|
|
|
|
|
| |
repl.mu now passing again. But still I have concerns:
a) Doubling backslashes in tests. Hard to tell how many levels to add.
b) I think the read-key interface needs to go. But then how do we handle
send-keys-to-channel and other flows like that in the chessboard app?
|
| | |
|
| | |
|
| |
|
|
|
| |
Some tests weren't actually running for the past 5 days.
Performed 5 why's.
|
| | |
|
| |
|
|
| |
Yet another repl bugfix.
|
| | |
|
| | |
|
| |
|
|
|
| |
I'd hoped finding that off-by-one error would fix the other intermittent
issues I've been seeing (commit 1512), but no they're still there.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Extracting a function for the prompt before starting to test it.
Still not clear how I should proceed. Need to express screen dependency
to 'run-interactive' somehow. Supporting generics might finally be on
the critical path.
|
| | |
|
| |
|
|
|
| |
But we really should test the top-level integration with
'run-interactive'.
|
| |
|
|
| |
Was missing a newline. More brittleness.
|
| |
|
|
|
|
| |
Just figured out why a first keystroke of backspace was sending me out
for a spin: run_interactive needs all early exits that don't actually
run anything to increment the current_step_index(). FML, this is lousy..
|
| | |
|
| |
|
|
| |
In the process we now support unicode in all mu strings!
|
| |
|
|
|
|
|
|
| |
I'm still having trouble with prematurely closed strings or strings
never being closed. Remember that when escaping brackets inside
scenarios you usually need two levels of escaping. The single-level is
a no-op and usually misleading. When brackets balance, don't bother
escaping. When they don't, escape twice.
|
| |
|
|
|
|
|
|
|
|
| |
As expected, I've already found two bugs in the repl during manual
testing. Still don't have a good characterization of when things go off
the rails.
But certainly hitting backspace too many times isn't messing things up
as I'd feared. Which might also be a bug, if the program isn't behaving
as I expect.
|
| |
|
|
|
|
|
| |
But I'm sure the next bug is nearby. And even if there's a solution
around here, the logic is now quite convoluted, with strings sometimes
returning on completion and sometimes recursing further in. We'll need
to rethink this.
|
| |
|
|
|
| |
slurp-string should sometimes return and sometimes recurse. Graah.
But the trace browser is awesome.
|
| |
|
|
|
| |
Ah, the failing test isn't what I thought. This is a regression.
Let's debug this using the trace-browser! Little tweak as I use it.
|
| |
|
|
| |
Aaalmost there..
|
| |
|
|
|
|
| |
More groundwork for dealing with backspacing back into string: instead
of simply exiting the current stack frame when the string completes,
create a *new* stack frame. More tests failing, but we're getting closer.
|
| |
|
|
|
| |
repl still needs to handle backspacing *back into* strings. This tries
to lay the groundwork.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Doesn't actually work interactively yet; for some reason it prints in
color, enter doesn't work, etc.
It'll be interesting to try to add color and history as separate
'layers' using before/after.
I'll also likely have to delete traces for its tests at some point as
they inevitably explode in size.
|
| | |
|
| |
|
|
|
|
| |
Swap printing generalized objects using arc's infrastructure to be the
$-prefixed debug helper, while the erstwhile $print-key-to-host becomes
the primitive print-character to host.
|
| |
|
|
| |
's-expression' is too jargon-y.
|
| |
|
|
|
| |
We'll never be able to avoid dying on syntax errors.
But hopefully we can make sessions easy to restore.
|
|
|
Next step: convenience features like balancing parens, coloring parens.
For that I'll have to leave line-based buffering behind.
My workflow seems to be spike-test-clean.
|