<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Convert C++ unit test from JUnit to CppUnit" href="https://bugs.freedesktop.org/show_bug.cgi?id=48024#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Convert C++ unit test from JUnit to CppUnit" href="https://bugs.freedesktop.org/show_bug.cgi?id=48024">bug 48024</a> from <a class="email" href="mailto:sbergman@redhat.com" title="Stephan Bergmann <sbergman@redhat.com>"> Stephan Bergmann</a> <pre>(In reply to <a href="show_bug.cgi?id=48024#c6">comment #6</a>) > I would like to look into this issue. Can someone give some pointers? new to > this The most obvious approach would be to translate individual so-called "complex" tests (see <a href="show_bug.cgi?id=48024#c1">comment 1</a>) from Java to C++. Those are largely self-contained tests that start and connect against an soffice instance (via Java org.openoffice.test.OfficeConnection; the C++ equivalent is in include/unotest/officeconnection.hxx) and then use remote UNO to trigger the code under test in the running soffice. The test code is typically located in */qa/complex/ directories (e.g., sw/qa/complex/checkColor/CheckChangeColor.java), and often makes use of helper functionality from qadevOOo/runner/util/ (for which there may or may not be C++ equivalents). Both building and running the tests is triggered by */JunitTest_*_complex.mk makefiles (e.g., sw/JunitTeste_sw_complex.mk). In a first approximation, a corresponding CppunitTest would still connect to an soffice process and access it via remote UNO, though in the long run it is of course more desirable to have the code under test small and self-contained enough so that it can run directly in the cppunit process.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>