[jbosstools-issues] [JBoss JIRA] (JBIDE-24873) Add management itests to eap jbds compatibility jenkins job

[ehsavoie Hugonnet (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-24873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13465169#comment-13465169 ] 

ehsavoie Hugonnet commented on JBIDE-24873:
-------------------------------------------

When we compare what is registered for security providers in a test to what is effectively registered in a real JBDS we see this : (quoting [~rob.stryker])
{code:java}
When tracing through SecurityProviderSaslClientFactory to locate differences between a working usecase (standalone java app)_ and failing usecase (mvn test suite), I discovered that inside createSaslClient(etc)...  

Successful standalone test:
  1 provider, named WildFlyElytronProvider
    - 185 services of various names

Failing mvn / unit test case:
  9 providers:
     - SUN (30 services)
     - SunRSASian (9 services)
     - SunEC (10 services)
     - SunJSSE (16 services)
     - SunJCE (131 services)
     - SunJGSS (2 services)
     - SunSASL (10 services)
     - XMLDSIG (13 services)
     - SunPCSC (1 service)

When the initial loop is over, checking clientFactoryList reveals:
Successful case:  27 Pair objects (returns LocalUserClient)
Failing mvn case: 6 pairs  (returns DigestMD5Client)
Real life JBDS: 27 Pair objects (returns LocalUserClient)
{code}
So it seems this is a configuration issue in how the testsuite runs; 
Please note that the testsuite use artifacts from a maven repo instead of a real JBDS installation. Maybe it is missing something in startup / config.

> Add management itests to eap jbds compatibility jenkins job
> -----------------------------------------------------------
>
>                 Key: JBIDE-24873
>                 URL: https://issues.jboss.org/browse/JBIDE-24873
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: server
>    Affects Versions: 4.5.0.Final
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>             Fix For: 4.5.1.AM2
>
>
> The EAP team would like us to add this test
> org.jboss.tools.as.management.itests
> to their compatibility job:
> https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/EAP7-JBDS/job/eap-7x-jbds-compatibility-jbosstools-4.4.3-RHEL/
> details here: EAP7-194
> The test to be added is run here:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-server-Run-Unit-and-ITests_master/
> Cc: [~rob.stryker]



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)