================ @@ -403,6 +403,70 @@ The 'child_send1.txt' file gets generated during the test run, so it makes sense TestSTTYBeforeAndAfter.py file to do the cleanup instead of artificially adding it as part of the default cleanup action which serves to cleanup those intermediate and a.out files. +## How To Test Specific Things + +Below is a breakdown of the layers in an lldb session, with hints for the type of +tests you can use to test these steps in isolation. + +If isolation is not possible, the fallback is always a Shell or API test that +works at a higher level. For these, try to be sure that the behaviour you are +checking for is not going to be generated by code other than the code in question, +now, or in the future. + +### Interactive user interface elements + +Like the text user interface, or tab completion in the command line interface. + +Use a `PExpectTest` or call the SBAPI equivalent of what the user's input is +doing. In completion's case, `SBCommandInterpreter::HandleCompletion`. + + ---------------- JDevlieghere wrote:
```suggestion ``` https://github.com/llvm/llvm-project/pull/205581 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
