Hi everyone :)Thanks to André's generous assistance, I now have testtool results for Windows XP and Linux (SuSE/RPM), to add to the collection begun with Shaun's kind provision of the testtool results for Mac OSX (Intel).
This is a huge help, which I appreciate very much. :)Now I need to know what to do with these results. I thought there would be other people new to QA who also could benefit from having these questions answered.
1. Which Linux build belongs to a machine running SuSe and using rpm packages? Is it Linux Intel or Linux x86? How do we distinguish between the two different Linux systems based on users' descriptions?
2. How do I manually check testtool errors? For example, the Linux results:
___Filename Errors Warnings Warnings_during_initialization ============================ ====== ======== ==============================
b_updt.res 1 1 3 ch_updt.res 0 0 3 closeoffice.res 0 0 3 c_updt.res 1 31 3 d_updt.res 0 1 3 first.res 0 9 3 f_updt_help.res 0 0 3 f_updt_pkgmgr.res 0 0 3 f_updt_spadmin.res 0 0 3 f_updt_templates.res 1 4 3 f_updt_windowfuncs.res 0 1 3 gallery.res 2 7 3 i_updt_1.res 0 0 3 i_updt_2.res 4 4 3 ma_updt.res 5 11 3 m_updt.res 0 2 3 oasis_graphics_update.res 0 2 3 topten.res 0 8 3 w_updt.res 5 6 3 ww_updt.res 3 2 3 xforms_updt.res 0 1 3======================================================================== ========
Total 21 files 22 90 63 ___show quite a few errors for some scripts. How do I trace those errors to the actions creating them?
3. What do we do for warnings about filter names? 4. What do errors citing "Invisible Window/Control" mean?Now we have a workaround for the scrambled Windows installer screens, and the testtool results, I plan to release our Windows build. Providing none of the above errors are serious, I will also release our Linux build (whichever one it turns out to be).
5. Based on the results for the RPM or DEB build of one Linux architecture, can I also release the other? (If not, that's four separate Linux builds requiring QA.)
In summary, it's a major step forward to be able to release the Windows build, and to be within spitting distance of releasing one of the Linux builds, since nearly all of our users run Windows or Linux. Thankyou very much for your help in making this possible. :)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN
PGP.sig
Description: This is a digitally signed message part
