Uploaded image for project: 'Thorntail'
  1. Thorntail
  2. THORN-1204

EAP quickstart tasks-jsf: one failing test


    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2017.6.0
    • Component/s: None
    • Labels:
    • Sprint:
      2017-Mar-B, 2017-Apr-A, 2017-May-A


      There's one test in the tasks-jsf EAP quickstart that fails on Swarm, yet passes on EAP/WildFly.

      Steps to reproduce:

      1. git clone -b 7.0.x https://github.com/jboss-developer/jboss-eap-quickstarts.git
      2. cd jboss-eap-quickstarts/tasks-jsf
      3. change version.jboss.bom.eap in pom.xml to 7.0.0.GA
      4. change pom.xml to include this profile:
      5. add src/test/resources/arquillian-swarm.xml file with this content:
        <?xml version="1.0" encoding="UTF-8"?>
        <arquillian xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://jboss.org/schema/arquillian" xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd">
            <container qualifier="wildfly-swarm" default="true">
                    <property name="host">localhost</property>
                    <property name="port">${swarm.arquillian.daemon.port:12345}</property>
      6. mvn clean test -Parq-wildfly-swarm

      With EAP/WildFly proper, all tests pass. With Swarm, one of the tests fail: ResourcesTest#facesContext_should_be_provided_from_current_context.

      The failing assertion checks that after doing FacesContext.setCurrentInstance(null), calling FacesContext.getCurrentInstance returns null. This appears to be true on EAP/WildFly, but with Swarm, the method returns com.sun.faces.config.InitFacesContext.

      This seems to be caused by some difference between WildFly and Swarm Arquillian adapters, though I couldn't pinpoint where. Both with WildFly and Swarm Arquillian adapters, the test seems to run on a thread that is different from the thread that runs the JSF initializers, so the FacesContext.threadInitContext shouldn't come to play... yet it seems it does. IDK. This is as far as I got.

      In any case, this seems to be a minor issue.

        Gliffy Diagrams




              • Assignee:
                mszynkie Michal Szynkiewicz
                lthon Ladislav Thon
              • Votes:
                0 Vote for this issue
                3 Start watching this issue


                • Created: