Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


https://bugs.freedesktop.org/show_bug.cgi?id=45904

--- Comment #14 from Ricardo <rivera151@gmail.com> ---
(In reply to comment #9)
So I'll try to add a few more details but I'm currently on vacation. So
please excuse if it is not in as much detail as it should be.

Currently our api test code is at qadevooo/tests/java/ and there in there in
the folders IFC and mod.

The implementation is divided between these two folders to represent our two
parts of the api implementations. The sender IFC part is for the interface
definition that is represented in our api through the IDL files in offapi
and can be found at api.LibreOffice.org. the mod part is for the actual
implementation that implements several interfaces.

We have a similar structure for the c++ tests. The test code for the
interfaces can be found in test/ and the code for the implementations for
calc in sc/qa/extras.

Each file in sc/qa/extras represents one implementation file and is one
cppunit test that is registered by a make file in sc/ and in
sc/module_sc.mk. the new tests just make it explicit which interfaces are
tested while it is implicitly done in the old java tests by querying for all
interfaces the object provides.

So we now need a two step process to convert old tests. First convert the
interface test code and implement it in test/ and secondly convert or better
write a clean new implementation for the api implementation.

The c++ implementation should however try to make the tests better by using
the assertion macros that are provided by cppunit, make explicit what was
implicit in the old implementation and improve the diagnostic messages. A
good start would be to look at some of Tue code that I already converted to
c++.

If you have more questions please ask and I'll try to answer as soon as
possible. I'll return next week from my vacation so I can answer questions
after that also by irc.

This is what needs to be done, if I interpreted correctly:
1. Pick a folder from qaDevOOo/tests/java/ifc (Pick an interface)
2. Implement the interface picked into test/source (Organized into folders as
in original implementation
3. Pick a folder from qaDevOOo/tests/java/mod (Test cases, organized in
folders, let's call it mod_name here)
4. Implement the tests into the folder mod_name/qa/extras (mod_name folder at
project root)

Is this correct?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.