[lldb-dev] Testing through api vs. commands

[Zachary Turner via lldb-dev]

On Wed, Oct 7, 2015 at 10:37 AM Zachary Turner <zturner at google.com> wrote:

> One more question: I mentioned earlier that we should enforce the
> distinction between HandleCommand tests and python api tests at an
> organizational level.  In other words, all HandleCommand tests go in
> lldb/test/command-api, and all new SB API tests go in
> lldb/test/command-api.
>
Sorry, ignore the part about all new SB API tests go in
lldb/test/command-api.  I meant to say python-api, and also this doesn't
need to be all new tests.  This is only the eventual goal (as described
below), so new SB API tests could continue to go where they do normally
(test/functionalities for example), and one day in the future when there
are no more HandleCommand tests in any of these folders, we can create the
python-api top level directory and move everything under there.


> Eventually the goal would be to only have 3 toplevel directories under
> lldb/test.  unittests, command-api, and python-api.  But this would take
> some time since it would be on a move-as-you-touch basis, rather than all
> at once.  Does this seem reasonable as well?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20151007/290fd35c/attachment.html>