Yes, I really wish unittest2 allowed non-aborting tests. If you split up all these tests, then you make the testsuite have to build and run some little executable over and over. It would be so nice if there were a way to say:
self.startTestBundle() self.assertTrue(something) ... self.assertTrue(something_else) self.endTestBundle() where the failures would be held in the test bundle till "endTestBundle", and then all the failures reported. That would allow us to test a bunch of independent things without having to build & run over and over. Jim > On Jun 21, 2018, at 11:41 AM, Greg Clayton via Phabricator via lldb-commits > <lldb-commits@lists.llvm.org> wrote: > > clayborg added a comment. > > It might be nice to split up the tests a bit. The data formatter tests have a > history of testing 1000 things at once and saying "something failed in the > this test with 1000 things". It would be nice if we knew that only > dictionaries were failing by testing each type individually. Not required for > this test, but try this out by reverting the changes in NSDictionary.cpp so > you can see the kind of issue I am talking about. > > > Repository: > rL LLVM > > https://reviews.llvm.org/D48450 > > > > _______________________________________________ > lldb-commits mailing list > lldb-commits@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
