herr kaste
herr kaste
That is currently not implemented. What I usually do is that I have a keyboard shortcut set ``` { "keys": ["ctrl+'"], "command": "pytest_toggle_panel" } ``` which will show/hide the output...
Yeah, sure, if I don't wear my TDD hat, I actually watch these dots as well, that's why I implemented this toggle panel command I just mentioned. I don't remember...
A persistent marker, or just flashing this at the end of the test run?
The history feature gets at least corrupt when you have "clones" or multiple views into the same buffer. That is easily reproducible.
To be fair, the whole "cursor history" feature is just sub-standard. If it works it jumps around in tiny steps; it seems more time-based (🙄) than actually location-based. Now, how...
Closing as stale
Interesting. `thenDoNothing` is just there because it reads nice, I guess. Or is there a specific reason to include it? Afaik we currently have: ``` # omit thenReturn and it...
Oh, didn't realize that `thenReturn()` or `thenAnswer()` without any args also works.
Well, ` when(values).appendleft(sample)` doesn't read good and I would probably not write it as well. I think `expect(values, times=1).appendleft(sample)` would read nice though. Because here `expect` means: be aware and...
Thanks for reporting. I think a equivalent reduced test case is just ``` from mockito import mock, when def test_foo(): x = mock() f1 = x.get_value when(x).get_value(10).thenReturn('foo') assert f1(10) ==...