[lldb-dev] Testing through api vs. commands

via lldb-dev lldb-dev at lists.llvm.org
Thu Sep 17 10:39:11 PDT 2015

On Thu, Sep 17, 2015 at 05:20:14PM +0000, Zachary Turner wrote:
> > > a) they should be explicitly marked as interface tests.
> > What's the decorator for this?
> There's not one currently.

Will there be?

> > > d) Results of these interface tests should also not be *verified* by the
> > > use of self.expect, but itself through the API.  (Relying on the text to
> > be
> > > formatted a specific way is obviously problematic, as opposed to just
> > > verifying the actual state of the debugger)
> >
> > How do you rely "on the text to be formatted a specific way"?
> Quick example: One of the most common patterns in the test are to do some
> things, print a backtrace, and run a regex against the output of the
> backtrace.   I've found at least 3 different examples of how this causes
> things to fail on Windows:

Oh, I misunderstood your point.  You're saying the existing tests rely
"on the text to be formatted a specific way".  Right.

I was asking how you *could* make sure the output was formatted a
specific way using the Python API.

More information about the lldb-dev mailing list