Thomas Roswall wrote:
now I removed the whole useproxy-check part of the iniinfo.inc and I am
up and running so far
I dont know if this vil invalidate the whole test - but at least I kan
du some tests now
if this is very bad, I hope that somebody will tell me.
It's ok, but since it sounds you are able to read basic code
let's try another thing with this function:
...
Thanks for the respons, I will do that during the weekend
Some of the results af the releasetest is difficult for me to evaluate. I
would like to send you the res-files with errors. Would it be OK?
/thomas roswall
To give you all an update of the results:
The results should be usefull to all of us;
1. Problem with 'UseProxy'
comment from Thomas:
it was a wrong cvsroot setting in the wincvs that caused the problem
or at least that is my guess, because i corrected the cvsroot,
deleted the
inc-file, checked out, and it worked
2. If you get errors, run the test again, to see if it is reproduceable.
It is GUI testing, that is not always that stable.
We can't do something about issues that occoured only once, but not
when the test is run again.
3. If you want to get an explanation to an error, always attach the whole
resultfile (the file ending with .res). Do not copy and paste just
a part into a mail.
4. Try to figure out what should happen yourself;
Double click onto the error message - that will bring you to the
basic code
that caused the error. There should be human readable comments what
the code is expected to do.
5. You don't need to do always a fresh checkout from cvs into a new
directory;
You do the checkout of qa/qatesttool one time, and from there you
just need
to update the checkout in that directory to get current updates.
The most reliable client is the cvs commandline;
There are error messages in some GUI cvs clients, that you don't get
on the
commandline.
6. Some problems are related to have no reference strings for that language;
If the test developer expects that strings are generated for his test as
reference that he will use during the test, he has to recognice the
absence
of these strings and put a clear message into his test how and where
to get/
put the string. If that is not clear, it is an issue to the test owner.
If you generate such strings for a language, tell them the test
owner, that
he puts them into cvs for future reference.
7. If you do a checkout on win32 there were some test documents unreadable
by OOo. That was because they hadn't the 'binary' flag in the cvs system.
The files I found in the calc project are fixed now.
8. The TestTool makes some changes to the behaviour of OOo.
- changeing the 'My documents' path
- deselecting the checkbox 'automatical file extension' in file save
dialogs
- ...
You don't need to reinstall, to revert the changes, just throw the
directory
with the user settings away.
The directory is shown on top of every test result:
** User configuration path : F:\Documents and
Settings\xxx\Application Data\OpenOffice.org2\
Just some thoughts...
cheers
thorsten
--
*******************************************************************
Thorsten Bosbach Sun Microsystems GmbH
Quality Assurance Engineer 20097 Hamburg, Germany
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
