Answers

• narayan Administrators

  July 2013

  Hi HadanMarv,
  
  Try adding

  <force>true</force>
  

  before

  </browserType>
  

  and check.
  
  It would look something like this:

  <browserType>
  <name>firefox-xvfb</name>
  <displayName>Firefox</displayName>
  <icon>firefox.png</icon>
  <path>env DISPLAY=:1 firefox</path>
  <options>-profile "$userDir/browser/ff/profiles/sahi$threadNo" -no-remote</options>
  <processName>firefox</processName>
  <capacity>5</capacity>
  <force>true</force>
  </browserType>
  

  
  
  Force makes Sahi ignore checking for path.
  
  Regards,
  Narayan
  
  
• HadanMarv Members

  July 2013

  Hi Narayan,
  
  Great, now we can't see the error message regarding firefox.
  But when we execute the sample script, it always running after 15 minutes.
  We can not see any log file regarding problems or errors.
  
  Could you tell us what is wrong, of if there is a place to see log file ?
  
  for information, at the beginning with the other configuration file (without force true), the test fall in error immediatly.
  
  Regards,
• globalworming Moderators

  July 2013

  I really can't recommend "force=true", Sahi usually recognizes the browser path just fine and if there's an error regarding that path, it can be taken seriously, as far as i know.
  So, it seems legit Sahi can't find "env Firefox" you somehow need to specify a display.
  
  I usually start sahi in Jenkins with "export DISPLAY=:1 sh sahi.sh". As sahi is starting the browser, firefox should get the right display.
  I just post my confg, you may find it valuable. Its with chromium, but firefox did work as well. And use the default browser_xml

  cd $SAHI_HOME/bin
  # path set to bin for some shell script sahi needs to call
  export PATH=$PATH:$SAHI_HOME/bin
  # XVFB_DISPLAY set in Jenkins config
  DISPLAY=$XVFB_DISPLAY sh sahi.sh &
  
  cleanup() {
    lsof -i:9999 -F p | cut -dp  -f2 | xargs kill
    pkill chromium-browse
    pkill Xvfb
    exit 1
  }
  trap "cleanup" 1 2 3 6 15 0
  
  echo "makes sure, Xvfb is running"
  ( test -z "$( pgrep Xvfb )" && ( Xvfb $XVFB_DISPLAY -screen 0 1280x768x24 & ) ) || echo "Xvfb is running"
  
  java -cp $SAHI_HOME/lib/ant-sahi.jar net.sf.sahi.test.TestRunner -test $WORKSPACE/nightlyNoShop.suite -browserType chromium \
  -baseURL http://sahi.example.com/_s_/dyn/Driver_initialized -host localhost -port 9999 -threads 1 -useSingleSession true \
  -initJS " \
  \$jenkinsBuildIndex='$BUILD_NUMBER'; \
  \$jenkinsTimestamp='$BUILD_ID'; \
  \$jenkinsJobName='$JOB_NAME'; \
  \$jenkinsSlave='$NODE_NAME'; \
  " \
  -htmlLog true \
  -htmlLogDir $WORKSPACE/target \
  -junitLog true \
  -junitLogDir  $WORKSPACE/target 
  
  
• HadanMarv Members

  July 2013

  After a long time of browsing google, we find a start of explanation.
  As we can read we have to install iceweasel instead of firefox.
  We continue to investigate to close this installation.
• globalworming Moderators

  July 2013

  I don't get how you come to this IMHO misguided conclusion, but if it works for you, go ahead