[JBoss JIRA] (JBDS-4067) Review labels shown for software components on confirmation page
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4067?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4067:
-----------------------------------
Assignee: Denis Golovin
> Review labels shown for software components on confirmation page
> ----------------------------------------------------------------
>
> Key: JBDS-4067
> URL: https://issues.jboss.org/browse/JBDS-4067
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.2.0.GA
>
>
> On confirmation page installer shows list of components from software stack. For most components there is detection algorithm that can find already installed components, so installer can skip install. There should be term selected for set of version for the required components:
> * required;
> * recommended;
> * tested;
> * ?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4010) DevSuite installer should check if virtualization extension is enabled
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4010?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-4010:
-----------------------------------
Assignee: Denis Golovin
> DevSuite installer should check if virtualization extension is enabled
> ----------------------------------------------------------------------
>
> Key: JBDS-4010
> URL: https://issues.jboss.org/browse/JBDS-4010
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.2.0.GA
>
>
> Oracle Virtualbox wont work w/o virtualization enabled in BIOS, so we should tell people to enable it for virtualbox to work after installation. Fortunately there is easy way to check it with powershell under windows.
> {code}PS C:\Users\eskimo> Get-WmiObject -class win32_processor -Property "VirtualizationFirmwareEnabled","SecondLevelAddressTr
> anslationExtensions"
> __GENUS : 2
> __CLASS : Win32_Processor
> __SUPERCLASS :
> __DYNASTY :
> __RELPATH :
> __PROPERTY_COUNT : 2
> __DERIVATION : {}
> __SERVER :
> __NAMESPACE :
> __PATH :
> SecondLevelAddressTranslationExtensions : True
> VirtualizationFirmwareEnabled : True
> PSComputerName :{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-3758) when something goes wrong, give user call to action / report of what went wrong
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3758?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3758:
-----------------------------------
Assignee: Denis Golovin
> when something goes wrong, give user call to action / report of what went wrong
> -------------------------------------------------------------------------------
>
> Key: JBDS-3758
> URL: https://issues.jboss.org/browse/JBDS-3758
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.2.0.GA
>
> Attachments: jbds-install-ste-failed-progress-bar-keeps-moving.png
>
>
> I attempted to install from Setup-bundled-0.0.2-20160401-33.exe and while the installer was OK with my using my pre-installed JDK 8 in C:\Program Files\Java\jdk1.8.0_25 (or C:\Program Files\Java\jre1.8.0_25) it then ran into a problem using that JDK to install JBDS.
> I noticed the problem at about 12% on the progress bar but it was still moving along at 45% when I grabbed the screenshot (attached).
> If a failure occurs, perhaps *we could change the bar from blue to red and move it to 100%* ?
> Also, should there be a call to action for the user?
> Even something simple like "*go check in C:\DeveloperPlatform\install.log for what might have happened*" would be useful here.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4089) Skip unit/ui tests not related to current platform/arch
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4089?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-4089.
---------------------------------
Assignee: Denis Golovin
Resolution: Rejected
UI and unit tests should cover all platform specific code and indicate that in test specs.
> Skip unit/ui tests not related to current platform/arch
> -------------------------------------------------------
>
> Key: JBDS-4089
> URL: https://issues.jboss.org/browse/JBDS-4089
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.GA
>
>
> Current UI tests are specific for windows. When installer supports Mac OS X there will be failures when UI tests are running on Mac. For example verification for Drive in selected path is valid only on Windows.
> this.skip() call does not work for protractor tests, because it still considered as a failure. Second option would be do not run tests that are not valid for current platform at all. That could be done ether by direct check in tests like
> {code}
> if(process.platform === 'win32') {
> it('test desctription', function(){
> // test instructions
> });
> }
> {code}
> or we can move platform specific tests in files with platform specific suffix and include them using process.platform and process.arch values at gulp execution time.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months