How to get involved in testing as volunteer Sent from my iPhone
> On Jan 10, 2018, at 10:43 AM, Kay Schenk <kay.sch...@gmail.com> wrote: > >> On Tue, Jan 9, 2018 at 1:46 PM, Andrea Pescetti <pesce...@apache.org> wrote: >> >> Kay Schenk wrote: >> >>> I know we have a number of Google tests incorporated currently. I don't >>> know much about how to construct these, but I'd like to help as well. >>> >> >> Sure, this would be very nice to have! >> >> But the discussion here (especially on the QA list) is mostly focused on >> manual testing by humans. So writing simple testcases down for the typical >> use of Writer, Calc and so on and then coordinating to execute them and >> share results. >> >> Let's keep the discussion about automated testing for the dev list; indeed >> Damjan already enabled some them in trunk and it would be good to have >> more. But this is a matter for developers, while QA volunteers will stay >> focused on the manual part. >> > > OK. I may have misconstrued Peter's initial comments about keeping the > "testing plan" on both the QA and DEV lists. In any case, I have found the > XML output from gtest buried in my build output, and will get back to DEV > on how we can use this. > > > >> >> Any thoughts on this? I would be happy to investigate. >>> >> >> It would be wonderful to have automated coverage for the 4.1.4 regressions >> to start with. This way we can guarantee that those bugs won't occur again >> in next releases. >> >> Regards, >> Andrea. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: dev-h...@openoffice.apache.org >> >> > > > -- > ---------------------------------------------------------------------- > MzK > > "Ring out the false, ring in the true." > -- poem "In Memoriam", Alfred Lord Tennyson
