> > > > I do still think we need some tests that verify commands run, but I > > > > think those tests should focus not on doing complicated interactions > > > > with the debugger, and instead just verifying that things parse > > > > correctly and the command is configured correctly, with the underlying > > > > functionality being tested by the api tests. > > > > > > > > Thoughts?
I agree that we should have both testing methods - SB API *and* commands, because we should be testing the user command interface too! Instead, to fix the Windows vs. other issue, I would suggest writing a sub-class that won't expect the missing params based on platform. In any case, there's a lot I never could figure out how to do in the SB API that I could only do via commands. For example, how do you test that a trailing space at the end of the expr --language option's argument is trimmed in the SB API? -Dawn _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
