On 11/21/13 3:21 PM, Daniel Nilsson wrote: > Thanks for the replies. > > Alexandro: Great I'll go through the intro for QA when im off from work. > > Jürgen: It sounds interesting and i have had a glance at googletest before. > However I think it might be a bit overwhelming to start with. Anyway I'll > check it out and see if it is something for me.
don't be shy, you can ask here on the list and it should be independent of many other things. The first step is to integrate the framework and make it available for general usage. You don't have to write complex unit test, that can evolve later on. The goal would be to make it usable in our buildenv which can be of course a challenge as well. The test framework is good documented which is good and will help to get started. Everything else can we figure our later Juergen > > Regards > Daniel > > > On Thu, Nov 21, 2013 at 2:54 PM, Jürgen Schmidt <jogischm...@gmail.com>wrote: > >> On 11/21/13 2:37 PM, Daniel Nilsson wrote: >>> Hi, >>> >>> I'm not sure if this mail should be sent to the dev, or user mailing >> list. >>> I have been working as a developer for a year now and I'm interesting in >>> learning more about testing. So i thought I'd look into the open source >>> scene. From what i have read, triage is a good place to start. >>> >>> My experience so far comes from writing automated test cases but I'm >>> interested in getting a wider knowledge in testing. >>> >> >> Hi Daniel, >> >> welcome to OpenOffice and your interest in testing and automated tests >> is perfect. We still have on our wish list the integration of new unit >> test framework because cppunit is license incompatible. >> >> I personally believe that the googletest framework [1] can be a good >> choice and I am asking if you are potentially interested to start >> something new going in this direction. It's an active project and is >> used in Google internal projects and in some popular projects like >> Chromium, LLVM. >> >> This would be a really cool project and we have to start with it sooner >> or later. What do you think? >> >> As first steps I would recommend to >> 1. set up your own build environment for AOO >> 2. integrate the googletest in our build process (compile the source >> from scratch in our env) >> 3. start using it by migrating some existing cppunit tests or implement >> new ones >> >> Again welcome at OpenOffice >> >> Juergen >> >> [1] http://code.google.com/p/googletest/ >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
