On 31/01/2019 19:26, Zachary Turner wrote:
Was the test failing specifically in the keyboard handler for up arrow, or was it failing in the command history searching code?  Because if it's the latter, then we could have a command which searches the command history.

The patch is r351313, if you want to look at it in detail. But, I don't think this one example matters too much, since we will always have some code which deals with the interactivity of the terminal. That will need to be tested somehow.

Another example: we have a fairly complex piece of code that makes sure our (lldb) prompt comes out in color. How do we write a test for that?
lldb-dev mailing list

Reply via email to