You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Jürgen Schmidt <jo...@gmail.com> on 2014/06/02 13:11:07 UTC
[CODE]: googletest is now available and can be used
Hi,
I have integrated googletest (gtest) in our build environment and it can
be used now. A first simple test in sal (sal/qa/sal) is using gtest now.
Some basic information and references can be found on [1]. See also the
related task id [2]
A further and deeper integration in gbuild (similar to cppunit) is
possible but not yet implemented.
Gtest is now a new prerequisite but can be easy disabled during the
configure step. Single tests can be disable highlevel in the makefile or
more fine grained in the sources. Details can be found on the wiki page [1].
Maybe some volunteers have interest to adapt further existing unit
tests, the idea is to migrate all existing tests from cppunit to gtest.
The main purpose of course is to make use of this new unit test
framework from the beginning for the planned work on a new improved
OOXML processing framework.
Juergen
[1] https://wiki.openoffice.org/wiki/Googletest
[2] https://issues.apache.org/ooo/show_bug.cgi?id=125003
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [CODE]: googletest is now available and can be used
Posted by jan i <ja...@apache.org>.
On 6 June 2014 23:43, Andrea Pescetti <pe...@apache.org> wrote:
> On 02/06/2014 Jürgen Schmidt wrote:
>
>> Maybe some volunteers have interest to adapt further existing unit
>> tests, the idea is to migrate all existing tests from cppunit to gtest.
>> ...
>> [1] https://wiki.openoffice.org/wiki/Googletest
>> [2] https://issues.apache.org/ooo/show_bug.cgi?id=125003
>>
>
> Why isn't this in a blog post? It is interesting, modern, suitable for new
> volunteers... it has everything to go there. I mean, of course we need to
> track this in Bugzilla and document it on the wiki, but neither of these
> two tools (or the dev list, for that matter) is effective for outreach.
> Nice things should be more visible.
>
+1 to a blog post.
rgds
jan I.
>
> Regards,
> Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
Re: [CODE]: googletest is now available and can be used
Posted by Jürgen Schmidt <jo...@gmail.com>.
On 06/06/14 23:43, Andrea Pescetti wrote:
> On 02/06/2014 Jürgen Schmidt wrote:
>> Maybe some volunteers have interest to adapt further existing unit
>> tests, the idea is to migrate all existing tests from cppunit to
>> gtest. ...
>> [1] https://wiki.openoffice.org/wiki/Googletest
>> [2] https://issues.apache.org/ooo/show_bug.cgi?id=125003
>
> Why isn't this in a blog post? It is interesting, modern, suitable for
> new volunteers... it has everything to go there. I mean, of course we
> need to track this in Bugzilla and document it on the wiki, but neither
> of these two tools (or the dev list, for that matter) is effective for
> outreach. Nice things should be more visible.
well it is not really spectacular, it is simply the replacement of
something we had before and we don't have migrated a lot of test by now.
Just a few and still a lot of work is necessary. But the main purpose
for me at the moment is to make it useable for the new OOXML framework
from the beginning.
But on the other hand it's time for a new blog post, I will see ...
Juergen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [CODE]: googletest is now available and can be used
Posted by Andrea Pescetti <pe...@apache.org>.
On 02/06/2014 Jürgen Schmidt wrote:
> Maybe some volunteers have interest to adapt further existing unit
> tests, the idea is to migrate all existing tests from cppunit to gtest. ...
> [1] https://wiki.openoffice.org/wiki/Googletest
> [2] https://issues.apache.org/ooo/show_bug.cgi?id=125003
Why isn't this in a blog post? It is interesting, modern, suitable for
new volunteers... it has everything to go there. I mean, of course we
need to track this in Bugzilla and document it on the wiki, but neither
of these two tools (or the dev list, for that matter) is effective for
outreach. Nice things should be more visible.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [CODE]: googletest is now available and can be used
Posted by Jürgen Schmidt <jo...@gmail.com>.
ok, after fixing some problems on the different platforms it seems to
work now at least on Linux, Mac and Windows. In the sal module some
tests are already migrated and can be used as samples for further migration.
It is straight forward and most tests are probably easy to migrate. But
as always the work have to be done. I hope some volunteers are
interested to help and start working on it.
Question or detailed discussion about problems or migration steps are
welcome here on the list and can be discussed.
Juergen
On 02/06/14 13:11, Jürgen Schmidt wrote:
> Hi,
>
> I have integrated googletest (gtest) in our build environment and it can
> be used now. A first simple test in sal (sal/qa/sal) is using gtest now.
>
> Some basic information and references can be found on [1]. See also the
> related task id [2]
>
> A further and deeper integration in gbuild (similar to cppunit) is
> possible but not yet implemented.
>
> Gtest is now a new prerequisite but can be easy disabled during the
> configure step. Single tests can be disable highlevel in the makefile or
> more fine grained in the sources. Details can be found on the wiki page [1].
>
> Maybe some volunteers have interest to adapt further existing unit
> tests, the idea is to migrate all existing tests from cppunit to gtest.
>
> The main purpose of course is to make use of this new unit test
> framework from the beginning for the planned work on a new improved
> OOXML processing framework.
>
> Juergen
>
>
> [1] https://wiki.openoffice.org/wiki/Googletest
> [2] https://issues.apache.org/ooo/show_bug.cgi?id=125003
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org