Issue 83529 - disble quickstarter at end of f_updt_wizard_firsttime.res
Summary: disble quickstarter at end of f_updt_wizard_firsttime.res
Status: CLOSED FIXED
Alias: None
Product: QA
Classification: Unclassified
Component: testscripts (show other issues)
Version: current
Hardware: PC Windows, all
: P3 Trivial
Target Milestone: ---
Assignee: joerg.skottke
QA Contact: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-11 09:42 UTC by andreschnabel
Modified: 2008-02-05 06:52 UTC (History)
1 user (show)

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

Attachments
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 andreschnabel 2007-11-11 09:42:38 UTC 
after f_updt_wizard_firsttime.res has been run, the Quickstarter is enabled. If
run in batch mode, some of the following test cases will fail, as the testtool
environment is not properly set up (I get an "No ActiveFrame for Desktop"
error). Unfortunately neither closeoffice.bat or kill seem to work properly in
that situation.

So please make sure, Quickstarter becomes disabled and closed after this test
has been finished.
Comment 1 joerg.skottke 2007-11-28 07:26:08 UTC 
Started
Comment 2 joerg.skottke 2007-11-28 08:12:04 UTC 
The test now ensures that the quickstarter is disabled in Tools/Options.
If you want it removed from memory, you need to restart the office afterwards.

Please report back whether this is sufficient or whether we really need to reset
the office after uncheking the quickstarter. I'd like to avoid that if possible.

Setting fixed.

@Andre: Can you please verify the fix in your environment? Thanks!
Comment 3 joerg.skottke 2007-11-28 08:30:59 UTC 
Ok, added a restart anyway. However, there are a lot of issues regarding the
quickstarter. As a last resort we started to rename the quickstarter binary
before running any test as we have no means of really getting the quickstarter
status from testtool.

My recommendation for you would be to do the same
Comment 4 andreschnabel 2008-02-05 06:52:32 UTC 
ok, wehn testinf OOH680m5 with current scripts