diff options
Diffstat (limited to 'testautomation/extensions')
4 files changed, 403 insertions, 403 deletions
diff --git a/testautomation/extensions/optional/input/options/readme.txt b/testautomation/extensions/optional/input/options/readme.txt index 39222957475c..da576203972d 100755 --- a/testautomation/extensions/optional/input/options/readme.txt +++ b/testautomation/extensions/optional/input/options/readme.txt @@ -1,195 +1,195 @@ -Important: The hander component extensionoptions.jar in the extensions may not
-contain exactly the same sources as the one build in the handler directory. To
-make sure that debugging works build the handler directory and put the
-extensionoptions.jar into the extension.
-
-
-
-leaf1.oxt: Defines a leaf under the node WriterNode
-================================================================================
-
-leaf2.oxt: Defines a leaf under a node that has a name which requires special
-"xml encoding". The name is "My Writer's & Settings". The node is not assigned
-to a Module and the Node/AllModules property is not true. This is a typical
-scenario when a Node had been added to an existing Module and later the Module
-was removed. This is a situation which actually should not occur. In this case
-DO NOT show the Node in the OOo's options dialog, because it shows only nodes
-for a particular module and in this case the Module for the Node is unknown.
-In the Extension Manager's
-options dialog this Node can be shown because the Module is irrelevant.
-See also nodes5.oxt.
-================================================================================
-
-leaves1.oxt: multiple ordered leaves under available nodes. The leaves Lables are
-localized for en-US and de. The following leaves should appear:
-
-Writer:
--leaves1 Writer 1 en-US
--leaves1 Writer 2 en-US
--leaves1 Writer 3 en-US
-
-Calc:
--leaves1 Calc 3 en-US
--leaves1 Calc 3 en-US
--leaves1 Calc 3 en-US
-
-Draw:
--leaves1 Draw 3 en-US
--leaves1 Draw 3 en-US
--leaves1 Draw 3 en-US
-
-If a german office is used then the strings contain "de" instead of "en-US".
-================================================================================
-
-leaves2.oxt: Same as leaves1.oxt. Use together with leaves1.oxt to test the
-grouping of leaves.
-================================================================================
-
-leaves3.oxt: Same as leaves1.oxt, but the leaves are not ordered.
-================================================================================
-
-nodes1.oxt: Defines one node which has AllModules set and which has
-no children. Therefore this node should not be displayed.
-================================================================================
-
-nodes2.oxt: Defines 3 nodes which use AllModules and which form an
-ordered group. Every node defines also 3 nodes which have a determined order.
-
--nodes2 node 1 en-US
- -nodes2 node 1 leaf 1 en-US
- -nodes2 node 1 leaf 2 en-US
- -nodes2 node 1 leaf 3 en-US
-
--nodes2 node 2 en-US
- -nodes2 node 2 leaf 1 en-US
- -nodes2 node 2 leaf 2 en-US
- -nodes2 node 2 leaf 3 en-US
-
--nodes2 node 3 en-US
- -nodes2 node 3 leaf 1 en-US
- -nodes2 node 3 leaf 2 en-US
- -nodes2 node 3 leaf 3 en-US
-
-================================================================================
-
-nodes3.oxt: Defines 3 nodes which are placed under different existing Modules.
-The nodes and there leaves are ordered.
-
-Context Writer:
-- nodes3 node 1
- nodes3 node 1 leaf 1 en-US
- nodes3 node 1 leaf 2 en-US
- nodes3 node 1 leaf 3 en-US
-
-- nodes3 node 2
- nodes3 node 2 leaf 1 en-US
- nodes3 node 2 leaf 2 en-US
- nodes3 node 2 leaf 3 en-US
-
-- nodes3 node 3
- nodes3 node 3 leaf 1 en-US
- nodes3 node 3 leaf 2 en-US
- nodes3 node 3 leaf 3 en-US
-
-Context Calc:
-- nodes3 node 1
- nodes3 node 1 leaf 1 en-US
- nodes3 node 1 leaf 2 en-US
- nodes3 node 1 leaf 3 en-US
-
-- nodes3 node 3
- nodes3 node 3 leaf 1 en-US
- nodes3 node 3 leaf 2 en-US
- nodes3 node 3 leaf 3 en-US
-
-Context Draw:
-- nodes3 node 2
- nodes3 node 2 leaf 1 en-US
- nodes3 node 2 leaf 2 en-US
- nodes3 node 2 leaf 3 en-US
-
-================================================================================
-
-nodes4.oxt: Same as nodes3.oxt. Use together with nodes3.txt to test the
-grouping of nodes.
-================================================================================
-
-nodes5.oxt: Defines a node which in turn defines 3 leaves. The Node
-is not assigned to a Module and the AllModule property is false (which is the
-default).This may happen when a node
-had been added to an already existing Module and then this Module was removed. For
-example, an extension adds a node to the "Writer Module" and the
-next office update removes the "Writer Module" (which is rather inconceivable).
-Then the node and its leaves MUST NOT be displayed in OOo's options dialog,
-because the Module is not known. However, it can be displayed in the
-options dialog of the Extension Manager. See also the description for leaf2.oxt.
-================================================================================
-
-modules1.oxt: Defines two Modules and three Nodes. The Nodes may not
-be displayed in OOo's options dialog because there is currently no application
-which uses this Module. However the Nodes are displayed in the options dialog
-of the Extension Manager.
-There are three Nodes defined. The relation ship is this:
-
--module1
- -node 1
- -leaf 1
- -leaf 2
- -leaf 3
- -node 2
- -leaf 1
- -leaf 2
- -leaf 3
- -node 3
- -leaf 1
- -leaf 2
- -leaf 3
-
--module2
- -node1
- -leaf 1
- -leaf 2
- -leaf 3
- -node3
- -leaf 1
- -leaf 2
- -leaf 3
-
-The options dialog of the Extension Manager shall display only three nodes:
-
- -node 1
- -leaf 1
- -leaf 2
- -leaf 3
- -node 2
- -leaf 1
- -leaf 2
- -leaf 3
- -node 3
- -leaf 1
- -leaf 2
- -leaf 3
-
-or
-
- -node 1
- -leaf 1
- -leaf 2
- -leaf 3
- -node 3
- -leaf 1
- -leaf 2
- -leaf 3
- -node 2
- -leaf 1
- -leaf 2
- -leaf 3
-
-Since the order of Module|s is not defined, the dialog may display first the
-Nodes from module2 and then from module1. If a node is already displayed then
-it is not shown again.
-
-================================================================================
-
-modules2.oxt: Same as modules1, except that the order of nodes and leaves
-is not defined.
+Important: The hander component extensionoptions.jar in the extensions may not +contain exactly the same sources as the one build in the handler directory. To +make sure that debugging works build the handler directory and put the +extensionoptions.jar into the extension. + + + +leaf1.oxt: Defines a leaf under the node WriterNode +================================================================================ + +leaf2.oxt: Defines a leaf under a node that has a name which requires special +"xml encoding". The name is "My Writer's & Settings". The node is not assigned +to a Module and the Node/AllModules property is not true. This is a typical +scenario when a Node had been added to an existing Module and later the Module +was removed. This is a situation which actually should not occur. In this case +DO NOT show the Node in the OOo's options dialog, because it shows only nodes +for a particular module and in this case the Module for the Node is unknown. +In the Extension Manager's +options dialog this Node can be shown because the Module is irrelevant. +See also nodes5.oxt. +================================================================================ + +leaves1.oxt: multiple ordered leaves under available nodes. The leaves Lables are +localized for en-US and de. The following leaves should appear: + +Writer: +-leaves1 Writer 1 en-US +-leaves1 Writer 2 en-US +-leaves1 Writer 3 en-US + +Calc: +-leaves1 Calc 3 en-US +-leaves1 Calc 3 en-US +-leaves1 Calc 3 en-US + +Draw: +-leaves1 Draw 3 en-US +-leaves1 Draw 3 en-US +-leaves1 Draw 3 en-US + +If a german office is used then the strings contain "de" instead of "en-US". +================================================================================ + +leaves2.oxt: Same as leaves1.oxt. Use together with leaves1.oxt to test the +grouping of leaves. +================================================================================ + +leaves3.oxt: Same as leaves1.oxt, but the leaves are not ordered. +================================================================================ + +nodes1.oxt: Defines one node which has AllModules set and which has +no children. Therefore this node should not be displayed. +================================================================================ + +nodes2.oxt: Defines 3 nodes which use AllModules and which form an +ordered group. Every node defines also 3 nodes which have a determined order. + +-nodes2 node 1 en-US + -nodes2 node 1 leaf 1 en-US + -nodes2 node 1 leaf 2 en-US + -nodes2 node 1 leaf 3 en-US + +-nodes2 node 2 en-US + -nodes2 node 2 leaf 1 en-US + -nodes2 node 2 leaf 2 en-US + -nodes2 node 2 leaf 3 en-US + +-nodes2 node 3 en-US + -nodes2 node 3 leaf 1 en-US + -nodes2 node 3 leaf 2 en-US + -nodes2 node 3 leaf 3 en-US + +================================================================================ + +nodes3.oxt: Defines 3 nodes which are placed under different existing Modules. +The nodes and there leaves are ordered. + +Context Writer: +- nodes3 node 1 + nodes3 node 1 leaf 1 en-US + nodes3 node 1 leaf 2 en-US + nodes3 node 1 leaf 3 en-US + +- nodes3 node 2 + nodes3 node 2 leaf 1 en-US + nodes3 node 2 leaf 2 en-US + nodes3 node 2 leaf 3 en-US + +- nodes3 node 3 + nodes3 node 3 leaf 1 en-US + nodes3 node 3 leaf 2 en-US + nodes3 node 3 leaf 3 en-US + +Context Calc: +- nodes3 node 1 + nodes3 node 1 leaf 1 en-US + nodes3 node 1 leaf 2 en-US + nodes3 node 1 leaf 3 en-US + +- nodes3 node 3 + nodes3 node 3 leaf 1 en-US + nodes3 node 3 leaf 2 en-US + nodes3 node 3 leaf 3 en-US + +Context Draw: +- nodes3 node 2 + nodes3 node 2 leaf 1 en-US + nodes3 node 2 leaf 2 en-US + nodes3 node 2 leaf 3 en-US + +================================================================================ + +nodes4.oxt: Same as nodes3.oxt. Use together with nodes3.txt to test the +grouping of nodes. +================================================================================ + +nodes5.oxt: Defines a node which in turn defines 3 leaves. The Node +is not assigned to a Module and the AllModule property is false (which is the +default).This may happen when a node +had been added to an already existing Module and then this Module was removed. For +example, an extension adds a node to the "Writer Module" and the +next office update removes the "Writer Module" (which is rather inconceivable). +Then the node and its leaves MUST NOT be displayed in OOo's options dialog, +because the Module is not known. However, it can be displayed in the +options dialog of the Extension Manager. See also the description for leaf2.oxt. +================================================================================ + +modules1.oxt: Defines two Modules and three Nodes. The Nodes may not +be displayed in OOo's options dialog because there is currently no application +which uses this Module. However the Nodes are displayed in the options dialog +of the Extension Manager. +There are three Nodes defined. The relation ship is this: + +-module1 + -node 1 + -leaf 1 + -leaf 2 + -leaf 3 + -node 2 + -leaf 1 + -leaf 2 + -leaf 3 + -node 3 + -leaf 1 + -leaf 2 + -leaf 3 + +-module2 + -node1 + -leaf 1 + -leaf 2 + -leaf 3 + -node3 + -leaf 1 + -leaf 2 + -leaf 3 + +The options dialog of the Extension Manager shall display only three nodes: + + -node 1 + -leaf 1 + -leaf 2 + -leaf 3 + -node 2 + -leaf 1 + -leaf 2 + -leaf 3 + -node 3 + -leaf 1 + -leaf 2 + -leaf 3 + +or + + -node 1 + -leaf 1 + -leaf 2 + -leaf 3 + -node 3 + -leaf 1 + -leaf 2 + -leaf 3 + -node 2 + -leaf 1 + -leaf 2 + -leaf 3 + +Since the order of Module|s is not defined, the dialog may display first the +Nodes from module2 and then from module1. If a node is already displayed then +it is not shown again. + +================================================================================ + +modules2.oxt: Same as modules1, except that the order of nodes and leaves +is not defined. diff --git a/testautomation/extensions/optional/input/platform/readme.txt b/testautomation/extensions/optional/input/platform/readme.txt index 25608fab37f9..2ab102a27d3c 100755 --- a/testautomation/extensions/optional/input/platform/readme.txt +++ b/testautomation/extensions/optional/input/platform/readme.txt @@ -1,49 +1,49 @@ -Extension which only support one platform
-========================================================
-
-freebsd_x86.oxt: freebsd_x86
-freebsd_x86_86.oxt: freebsd_x86_64
-linux_arm_eabi.oxt: linux_arm_eabi
-linux_arm_oabi.oxt: linux_arm_oabi
-linux_ia64.oxt: linux_ia64
-linux_mips_eb.oxt: linux_mips_eb
-linux_mips_el.oxt: linux_mips_el
-linux_powerpc64.oxt: linux_powerpc64
-linux_powerpc.oxt: linux_powerpc
-linux_s390.oxt: linux_s390
-linux_s390x.oxt: linux_s390x
-linux_sparc.oxt: linux_sparc
-linux_x86.oxt: linux_x86
-linux_x86_64.oxt: linux_x86_64
-macos_powerpc.oxt: macos_powerpc
-macos_x86.oxt: macos_x86
-solaris_sparc.oxt: solaris_sparc
-solaris_x86.oxt: solaris_x86
-windows_x86.oxt: windows_x86
-os2_x86.oxt: os/2_x86
-
-Extensions which support multiple platforms
-=======================================================
-mul1.oxt: windows_x86, linux_x86, solaris_x86
-
-
-All platforms
-=========================================================
-all1.oxt: all, The <platform> element is missing. Default is "all".
-
-all2.oxt: all, <platform value="all" />
-
-all3.oxt: all, no description.xml
-
-
-
-Invalid platforms
-=========================================================
-The following extensions cannot be installed because the platform element
-is not correct. We assume that no valid platform is defined.
-
-invalid1.oxt: <platform />
-
-invalid2.oxt: <platform value=""/>
-
-invalid3.oxt: <platform value="," />
+Extension which only support one platform +======================================================== + +freebsd_x86.oxt: freebsd_x86 +freebsd_x86_86.oxt: freebsd_x86_64 +linux_arm_eabi.oxt: linux_arm_eabi +linux_arm_oabi.oxt: linux_arm_oabi +linux_ia64.oxt: linux_ia64 +linux_mips_eb.oxt: linux_mips_eb +linux_mips_el.oxt: linux_mips_el +linux_powerpc64.oxt: linux_powerpc64 +linux_powerpc.oxt: linux_powerpc +linux_s390.oxt: linux_s390 +linux_s390x.oxt: linux_s390x +linux_sparc.oxt: linux_sparc +linux_x86.oxt: linux_x86 +linux_x86_64.oxt: linux_x86_64 +macos_powerpc.oxt: macos_powerpc +macos_x86.oxt: macos_x86 +solaris_sparc.oxt: solaris_sparc +solaris_x86.oxt: solaris_x86 +windows_x86.oxt: windows_x86 +os2_x86.oxt: os/2_x86 + +Extensions which support multiple platforms +======================================================= +mul1.oxt: windows_x86, linux_x86, solaris_x86 + + +All platforms +========================================================= +all1.oxt: all, The <platform> element is missing. Default is "all". + +all2.oxt: all, <platform value="all" /> + +all3.oxt: all, no description.xml + + + +Invalid platforms +========================================================= +The following extensions cannot be installed because the platform element +is not correct. We assume that no valid platform is defined. + +invalid1.oxt: <platform /> + +invalid2.oxt: <platform value=""/> + +invalid3.oxt: <platform value="," /> diff --git a/testautomation/extensions/optional/input/update/readme.txt b/testautomation/extensions/optional/input/update/readme.txt index 9e1096576017..e48fa3db5ff3 100755 --- a/testautomation/extensions/optional/input/update/readme.txt +++ b/testautomation/extensions/optional/input/update/readme.txt @@ -1,26 +1,26 @@ -The folder contains only simple extension. That is, they only contain
-- META-INF
--t.rdb
--description.xml
-
-The description.xml contains only a version and one URL to the update data
-
-For example:
-
-
-<?xml version="1.0" encoding="UTF-8"?>
-<description xmlns="http://openoffice.org/extensions/description/2006"
- xmlns:xlink="http://www.w3.org/1999/xlink">
- <version value="1.0" />
-
- <update-information>
- <src xlink:href="http://extensions.openoffice.org/testarea/desktop/simple/plain1.update.xml" />
- </update-information>
-</description>
-
-
-The update information which is referenced in the update-information and the update is committed in the extensions/www project. To modify them get the project:
-
-cvs co extensions/wwww
-
-the files can be found under extensions/www/testarea/desktop
+The folder contains only simple extension. That is, they only contain +- META-INF +-t.rdb +-description.xml + +The description.xml contains only a version and one URL to the update data + +For example: + + +<?xml version="1.0" encoding="UTF-8"?> +<description xmlns="http://openoffice.org/extensions/description/2006" + xmlns:xlink="http://www.w3.org/1999/xlink"> + <version value="1.0" /> + + <update-information> + <src xlink:href="http://extensions.openoffice.org/testarea/desktop/simple/plain1.update.xml" /> + </update-information> +</description> + + +The update information which is referenced in the update-information and the update is committed in the extensions/www project. To modify them get the project: + +cvs co extensions/wwww + +the files can be found under extensions/www/testarea/desktop diff --git a/testautomation/extensions/optional/input/web_update/readme.txt b/testautomation/extensions/optional/input/web_update/readme.txt index cc87a86d0b33..4ae5ddd9182f 100755 --- a/testautomation/extensions/optional/input/web_update/readme.txt +++ b/testautomation/extensions/optional/input/web_update/readme.txt @@ -1,133 +1,133 @@ -The folder contains extensions which need to be updated through a web site.
-The "Updates dialog" of the Extension Manager will mark the updates for these
-extensions as "browser based update". The Extension Manager will open a browser
-for each of the extensions and navigate to the respective website.
-
-================================================================================
-web1.oxt - web5.oxt:
-================================================================================
-They contain <update-information>. That is they reference directly the respective
-webX.update.xml (for example, web1.update.xml) files which are available at
-http://extensions.openoffice.org/testarea/desktop/website_update/update/...
-For example:
-http://extensions.openoffice.org/testarea/desktop/website_update/update/web2.update.xml
-
-The update information contain multiple URLs to "localized" web sites. Each URL is
-assigned to a particular local. For example:
-
-<src xlink:href="http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_de.html" lang="de"/>
-
-The Extension Manager will choose the URLs where the lang attribute matches most
-closely the locale of the office.
-
-The following table shows what localized web site is used, when the office uses the locale
-en-US. The web page will display the locale used. See update/web1_de.html, etc.
-
-
-Localization:
-
-Installed office en-US
- | publisher | release notes
-=============================================
-web1.oxt | en-US | en-US
----------------------------------------------
-web2.oxt | en-US-region1 | en-US-region1
----------------------------------------------
-web3.oxt | en | en
----------------------------------------------
-web4.oxt | en-GB | en-GB
----------------------------------------------
-web5.oxt | de | de
-
-
-================================================================================
-web6.oxt
-================================================================================
-Need not be committed in extensions/www/testarea/desktop.
-
-web6.oxt is intended for tests with extensions.services.openoffice.org.
-It does not contain <update-information>. That is, the Extension Manager will obtain
-the update information from the repository as feed:
-
-http://updateext.services.openoffice.org/ProductUpdateService/check.Update
-
-Test
-----
-Repository:
-
--Create the new extension in the repository.
--Provide a company name and a URL to the company website. In our case this should be
- http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
-
--Create a new release for the extension. Upload the description.xml of version 2.0
-(update/web6/description.xml). Provide a download URL for the web site (field
- "Download from page / Open follow up page URL", which should be
- http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
- Provide release notes.
-
-
-Office:
--Install version 1.0 of the extension:
- desktop/test/deployment/update/website_update/web6.oxt
-
--Run the update in the Extension Manager
-
-
-Result:
-The Update Dialog should show the publisher name as provided in "Provider URL" field
-of the extension edit page (not release).
-
-A release notes link is displayed with an URL to the release notes as provided in
-the "Provider Title" field of the extension release edit page.
-
-When running the update then the web browser should navigate to
-http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
-
-
-================================================================================
-web7.oxt
-================================================================================
-Need not be committed in extensions/www/testarea/desktop
-
-web7.oxt is intended for tests with extensions.services.openoffice.org.
-It does not contain <update-information>. That is, the Extension Manager will obtain
-the update information from the repository as feed:
-
-http://updateext.services.openoffice.org/ProductUpdateService/check.Update
-
-The description.xml which will be uploaded contains URLs for release notes and publisher
-names/ URLs. That is, these information are not generated from the information of the
-repository web site.
-
-Test
------------
-Repository:
-
--Create the new extension in the repository.
--Provide a company name and a URL to the company website. In our case these should be different
- to those provided in the description.xml. These should NOT go into the update feed.
- Choose for example as "Provider Title": FOO and as "Provider URL" some valid URL but NOT
- http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
-
--Create a new release for the extension. Upload the description.xml of version 2.0
-(update/web7/description.xml). Provide a download URL for the web site (field
- "Download from page / Open follow up page URL", which should be
- http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
- Provide release notes.
-
-Office:
--Install version 1.0 of the extension:
- desktop/test/deployment/update/website_update/web7.oxt
-
--Run the update in the Extension Manager
-
-Result:
-The Update Dialog should show the publisher name as provided in the description.xml.
-That is: My OpenOffice en-US and NOT "FOO".
-
-A release notes link is displayed with an URL to the release notes as provided in
-the description.xml. That is:
-http://extensions.openoffice.org/testarea/desktop/publisher/release-notes_xxx.html
-
-When running the update then the web browser should navigate to
-http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html
+The folder contains extensions which need to be updated through a web site. +The "Updates dialog" of the Extension Manager will mark the updates for these +extensions as "browser based update". The Extension Manager will open a browser +for each of the extensions and navigate to the respective website. + +================================================================================ +web1.oxt - web5.oxt: +================================================================================ +They contain <update-information>. That is they reference directly the respective +webX.update.xml (for example, web1.update.xml) files which are available at +http://extensions.openoffice.org/testarea/desktop/website_update/update/... +For example: +http://extensions.openoffice.org/testarea/desktop/website_update/update/web2.update.xml + +The update information contain multiple URLs to "localized" web sites. Each URL is +assigned to a particular local. For example: + +<src xlink:href="http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_de.html" lang="de"/> + +The Extension Manager will choose the URLs where the lang attribute matches most +closely the locale of the office. + +The following table shows what localized web site is used, when the office uses the locale +en-US. The web page will display the locale used. See update/web1_de.html, etc. + + +Localization: + +Installed office en-US + | publisher | release notes +============================================= +web1.oxt | en-US | en-US +--------------------------------------------- +web2.oxt | en-US-region1 | en-US-region1 +--------------------------------------------- +web3.oxt | en | en +--------------------------------------------- +web4.oxt | en-GB | en-GB +--------------------------------------------- +web5.oxt | de | de + + +================================================================================ +web6.oxt +================================================================================ +Need not be committed in extensions/www/testarea/desktop. + +web6.oxt is intended for tests with extensions.services.openoffice.org. +It does not contain <update-information>. That is, the Extension Manager will obtain +the update information from the repository as feed: + +http://updateext.services.openoffice.org/ProductUpdateService/check.Update + +Test +---- +Repository: + +-Create the new extension in the repository. +-Provide a company name and a URL to the company website. In our case this should be + http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html + +-Create a new release for the extension. Upload the description.xml of version 2.0 +(update/web6/description.xml). Provide a download URL for the web site (field + "Download from page / Open follow up page URL", which should be + http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html + Provide release notes. + + +Office: +-Install version 1.0 of the extension: + desktop/test/deployment/update/website_update/web6.oxt + +-Run the update in the Extension Manager + + +Result: +The Update Dialog should show the publisher name as provided in "Provider URL" field +of the extension edit page (not release). + +A release notes link is displayed with an URL to the release notes as provided in +the "Provider Title" field of the extension release edit page. + +When running the update then the web browser should navigate to +http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html + + +================================================================================ +web7.oxt +================================================================================ +Need not be committed in extensions/www/testarea/desktop + +web7.oxt is intended for tests with extensions.services.openoffice.org. +It does not contain <update-information>. That is, the Extension Manager will obtain +the update information from the repository as feed: + +http://updateext.services.openoffice.org/ProductUpdateService/check.Update + +The description.xml which will be uploaded contains URLs for release notes and publisher +names/ URLs. That is, these information are not generated from the information of the +repository web site. + +Test +----------- +Repository: + +-Create the new extension in the repository. +-Provide a company name and a URL to the company website. In our case these should be different + to those provided in the description.xml. These should NOT go into the update feed. + Choose for example as "Provider Title": FOO and as "Provider URL" some valid URL but NOT + http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html + +-Create a new release for the extension. Upload the description.xml of version 2.0 +(update/web7/description.xml). Provide a download URL for the web site (field + "Download from page / Open follow up page URL", which should be + http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html + Provide release notes. + +Office: +-Install version 1.0 of the extension: + desktop/test/deployment/update/website_update/web7.oxt + +-Run the update in the Extension Manager + +Result: +The Update Dialog should show the publisher name as provided in the description.xml. +That is: My OpenOffice en-US and NOT "FOO". + +A release notes link is displayed with an URL to the release notes as provided in +the description.xml. That is: +http://extensions.openoffice.org/testarea/desktop/publisher/release-notes_xxx.html + +When running the update then the web browser should navigate to +http://extensions.openoffice.org/testarea/desktop/website_update/update/web1_en-US.html |