Re: [Libreoffice-qa] minutes of ESC call ...
On Fri, May 15, 2015 at 11:14 AM, Pedro wrote: > Norbert Thiebaud wrote >> + The points where we think there _may_ be still some issue that need >> actual user-gui testing (like VclPtr) can be tested just as well with >> a Beta release. >> >> For these reasons tweaking/reducing the beta-period is not warranted. > > Fair enough. > > What is VclPtr? I could not find any reference to it in the Release Notes. it is a fairly big, and potentially disruptive _internal_ change. it has no user-visible attributes it is about how vlc objects -- vcl is the visual components library, which is responsible for the abstraction of just about anything that make its way on your screen -- life cycle is handled. > > Which items need user testing? every windows, every dialog, every tabs, in general an as complete as possible exercise of any gui item, as this change _can_ reveal life-cycle management issue with these objects.. in case of problems, the symptom will likely be 'crash' Norbert ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] minutes of ESC call ...
Norbert Thiebaud wrote > + The points where we think there _may_ be still some issue that need > actual user-gui testing (like VclPtr) can be tested just as well with > a Beta release. > > For these reasons tweaking/reducing the beta-period is not warranted. Fair enough. What is VclPtr? I could not find any reference to it in the Release Notes. Which items need user testing? -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-minutes-of-ESC-call-tp4148598p4148682.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] minutes of ESC call ...
On Fri, May 15, 2015 at 5:51 AM, Pedro wrote: > Michael Meeks-5 wrote >> + BugHunting Session 5.0: One week away! >> + hoping for new people > > It would be more useful to do a BugHunting session with RC1 (because it > installs to the default folder and uses the real profile) than with Beta1 > I think it would be worth to give RC1 a longer test period because this is a > major version change. Maybe skip Beta1 and release RC1 sooner? https://wiki.documentfoundation.org/ReleasePlan/5.0 + RC1 is cut a month and a half before release... as usual with .0 there is a longer period between RC1 and release. + From a 'profile' point of view this _not_ a major release, so there is not big 'profile migration'. iow the difference between Beta1 and RC1 should be minimal + The points where we think there _may_ be still some issue that need actual user-gui testing (like VclPtr) can be tested just as well with a Beta release. For these reasons tweaking/reducing the beta-period is not warranted. Norbert ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] minutes of ESC call ...
Michael Meeks-5 wrote > + BugHunting Session 5.0: One week away! > + hoping for new people It would be more useful to do a BugHunting session with RC1 (because it installs to the default folder and uses the real profile) than with Beta1 I think it would be worth to give RC1 a longer test period because this is a major version change. Maybe skip Beta1 and release RC1 sooner? Just my 2cents ;) -- View this message in context: http://nabble.documentfoundation.org/Libreoffice-qa-minutes-of-ESC-call-tp4148598p4148656.html Sent from the QA mailing list archive at Nabble.com. ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
Re: [Libreoffice-qa] minutes of ESC call ...
On 14.05.2015 16:47, Michael Meeks wrote: > + can't run make check: seems to fail badly with ssh build. > + database related stuff seems to require a display. > + 'make' says waiting for rest to finish > + tons of Java/JUnit not moving / exiting. > + concerned wrt. Java etc. > + would love gdb backtracing through Java (Michael) > + JUnit tests not in-process (Markus) in case of a crash, you already get the Java backtrace in tinderbox failure mails: it is printed on the next UNO call, and it's always something like "com.sun.star.lang.DisposedException: java_remote_bridge" (unless the test does something stupid and somehow suppresses printing of the exception backtrace). but you have to manually combine this Java backtrace with the C++ backtrace printed by gdb. also at least for the unoapi tests the Java backtrace can be quite unhelpful if it's one of the overly generic object-oriented tests like the XPropertySet ones; the printed LOG output is more helpful then. > + need a more systematic UX testing thing (Michael) > + yes - would like to have something (Markus) > + propose talk in the conference > + new UX stuff provides nice ways to get it working. > + an incremental way to test it. > + possible to create a robust way to test UX (Michael) > + do the 80/20 rule (Norbert) > + something reliable & simple needed (Markus) i'd hope the A11y interfaces could be useful for UI testing - that should make the tests relatively robust against cosmetic changes to the UI, and a11y needs testing anyway. e.g. something like this looks promising: http://ldtp.freedesktop.org/wiki/ ___ List Name: Libreoffice-qa mailing list Mail address: Libreoffice-qa@lists.freedesktop.org Change settings: http://lists.freedesktop.org/mailman/listinfo/libreoffice-qa Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://lists.freedesktop.org/archives/libreoffice-qa/
