Issue 115042 - Need possibility to enable/disable extensions via cli switch and API
Summary: Need possibility to enable/disable extensions via cli switch and API
Status: CONFIRMED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m88
Hardware: All All
: P4 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-13 07:24 UTC by joerg.skottke
Modified: 2013-08-07 15:31 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
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 joerg.skottke 2010-10-13 07:24:44 UTC 
Requirement for automated testing:

We need a way to enable/disable extensions at will. This should be possible from
the command line and via API call.

Reason:

QA Automation cannot handle changing UI content with reasonable effort. This
also conflicts with the general QA paradigm to have static, measurable values.
If we test extensions, we should be able to enable the single extension to be
tested while disabling all interfering others.
Comment 1 joerg.skottke 2010-10-13 07:26:51 UTC 
Fix typo in summary
Comment 2 b.osi.ooo 2010-11-09 09:15:19 UTC 
added cc
Comment 3 joachim.lingner 2011-02-16 12:42:30 UTC 
.
Comment 4 joachim.lingner 2011-02-16 12:57:28 UTC 
.
Comment 5 Olaf Felka 2011-02-16 13:23:38 UTC 
I don't think that requirements for testautomation are P4.