Issue 69527 - Testing-order in Topten.Bas causes problems.
Summary: Testing-order in Topten.Bas causes problems.
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: Build Tools
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.1
Assignee: fredrik.haegg
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-14 13:25 UTC by fredrik.haegg
Modified: 2006-09-15 11:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Testtool-Resultfile (91.82 KB, application/octet-stream)
2006-09-15 10:11 UTC, fredrik.haegg 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description fredrik.haegg 2006-09-14 13:25:40 UTC 
When running the topten.bas-test on some machines, the current testing-order
causes problems. 

But when changing the current order from this: 
WRITER
CALC
IMPRESS
DRAW
MATH
HTML
MASTERDOC

to this: 

MATH
HTML
MASTERDOC
WRITER
CALC
IMPRESS
DRAW

it works without any problems.
Comment 1 b.osi.ooo 2006-09-14 20:25:49 UTC 
my one ;-)

would you please outline the problems?
maybe by attaching the result file....

usually the test isn't the problem - you have to write
an issue for the OOo product, not for the test.
Comment 2 fredrik.haegg 2006-09-15 10:11:58 UTC 
Created attachment 39164 [details]
Testtool-Resultfile
Comment 3 fredrik.haegg 2006-09-15 10:12:51 UTC 
Attached resultfile. Changed owner.
Comment 4 b.osi.ooo 2006-09-15 11:27:22 UTC 
ok, now seeing the result file:

1. this test works this way for 'years'
2. I won't change this test just because it runs without errors when
   changing the run order of the test cases
3. The difference in the return stream looks like some one else on this machine
is using the same port for testing - make sure you port is unique on the
machine: Extras->Settings->Misc: Testtool Port
else:
4. The experience showed that errors have their reasons in OOo, not in the tests.

-> closing as invalid
Comment 5 b.osi.ooo 2006-09-15 11:28:27 UTC 
invalid
Comment 6 b.osi.ooo 2006-09-15 11:29:07 UTC 
closing