[JBoss JIRA] (JBTIS-574) Adapt UI tests to 8.0.0
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-574?page=com.atlassian.jira.plugin.... ]
Tomáš Sedmík updated JBTIS-574:
-------------------------------
Labels: (was: fus)
> Adapt UI tests to 8.0.0
> -----------------------
>
> Key: JBTIS-574
> URL: https://issues.jboss.org/browse/JBTIS-574
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 4.3.0.Alpha2
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Priority: Critical
> Fix For: 4.3.0.Final
>
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> There are some changes in Fuse Tooling (new Camel Editor, ...), so our automated tests have to be adapted to reflect these changes.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3643) Installer - Should display a unique build identifier
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3643?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-3643.
-----------------------------
Verified with installer build from 2016-03-15 source.
> Installer - Should display a unique build identifier
> -----------------------------------------------------
>
> Key: JBDS-3643
> URL: https://issues.jboss.org/browse/JBDS-3643
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.GA
> Reporter: Len DiMaggio
> Assignee: Joshua Wilson
> Labels: havoc, ui
> Fix For: 9.1.0.CR1
>
>
> This affects QE immediately, and may affect customers too. The installer UI should display a unique identifier (version number). Having a build number displayed in the UI will assist QE in testing as we iterate through the various versions of the installer. Thx!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21815) Image metadata not refreshed after name change
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21815?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21815:
---------------------------------------
Issue should be fixed with JBIDE-21868. Waiting to review on https://github.com/jbosstools/jbosstools-openshift/pull/1030
> Image metadata not refreshed after name change
> ----------------------------------------------
>
> Key: JBIDE-21815
> URL: https://issues.jboss.org/browse/JBIDE-21815
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> Steps to reproduce:
> - open the *Deploy Docker Image* wizard
> - input/search for {{jboss/infinispan-server:8.1.0.Final}}, then click on {{Next}}. The *Deploy Configuration & Scalability* page should show a handful of metadata, including {{INFINISPAN_VERSION = 8.1.0.Final}}
> - go back to the previous page, *Deploy an Image* and now input/search for {{jboss/wildfly:10.0.0.Final}} and click back on {{Next}} again.
> - ASSERT: the metadata should have been updated
> - FAILED: the metadata displayed correspond to the previously selected {{jboss/infinispan-server:8.1.0.Final}} Docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21868) Performance issue on Deploy Docker Image wizard
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21868?page=com.atlassian.jira.plugi... ]
Xavier Coulon reassigned JBIDE-21868:
-------------------------------------
Assignee: Jeff Cantrill (was: Xavier Coulon)
[~jcantrill] could you have a look at this patch, please ?
> Performance issue on Deploy Docker Image wizard
> -----------------------------------------------
>
> Key: JBIDE-21868
> URL: https://issues.jboss.org/browse/JBIDE-21868
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.CR1
>
>
> When the user inputs an image name in the "Deploy Docker Image" wizard, there is a performance issue due to the fact that some data are initialized as the user inputs the image name.
> This is even more significant if the user wants to use an image that was not pulled, i.e., a remote call will be performed for each new character typed in the {{Image Name}} field.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years