Fitnesse from Command line


In continuation to my previous post "Integrating QC with Fitnesse"
Here are the commandline options for running Fitnesse:

Advantages:
  1. All tests run in a single process unlike the web server test executions.
  2. It's easily debuggable.
  3. It removes the need to start a local FitNesse server to run tests.
  4. Can generate HTML output to a file
  5. Can generate XML output to a file
Sample Command:
java -jar fitnesse.jar -p "&strPort&" -c "&strFITTestScriptName&" > "&strExpectedResultsPath

Command line options:
  1. -debug
    This option will print FitNesse protocol actions to the console.
  2. -v
    This option should give a verbose output about test progress to the console
  3. -results file
    The result of the testrun is saved to a textfile with the given name.
  4. -html file
    The result of the testrun is saved to a html file with the given name.
  5. -xml file
    The result of the testrun is saved to a xml file with the given name.
  6. -nopath
    This option will make FitNesse ignore !path options specified in the wiki pages.
  7. -suiteFilter filter
    Specifying a filter will only run pages with tags matching the filter.

Comments

  1. Charles F. Radley2/7/16

    The sample command does not, it gives me a usage message, something is therefore missing ...C:\Selenium>java -jar fitnesse-standalone.jar -p "&strPort&" -c "&strFITTestScriptName&"
    Usage: java -jar fitnesse.jar [-vpdrlfeoaicb]
    -p {80}
    -d {.}
    -r {FitNesseRoot}
    -l {no logging}
    -f {plugins.properties}
    -e {14} Number of days before page versions expire
    -o omit updates
    -a {user:pwd | user-file-name} enable authentication.
    -i Install only, then quit.
    -c execute single command.
    -b redirect command output.
    -v {off} Verbose logging

    C:\Selenium>

    ReplyDelete

Post a Comment

Popular posts from this blog

Software Testing @ Microsoft

Image
In continuation from my previous  series of posts  targeting testing in top few companies from the technology space. After  Software Testing @Facebook  and @Google  we shall now look at Microsoft: Testing@Microsoft Software Development Engineers in Test (SDETs) are usually just called Test and sometimes Software Testing. SDETs are responsible for maintaining high testing and qualityassurance standards for all Microsoft products. Software Development Engineers (SDEs) are often referred to as Software Development. SDEs write the code that drives Microsoft products and upgrades. Very few teams in Microsoft are still using SDETs to do significant amount of manual testing. Manual testing is mainly outsourced. Actually, as early as in 2004, for example, most of the manual testing of MSN Explorer was outsourced. Think about it this way: it just doesn't make sense for test manager to spend their headcount (SDETs) on something can be easily outsourced.  Until 2005, Microso
Read more

Trim / Remove spaces in Xpath?

Image
If you are wondering how you can trim the spaces in your xpath, this is how: The normalize-space function strips leading and trailing white-space from a string, replaces sequences of white-space characters by a single space, and returns the resulting string. Example : Which one is better? //td[starts-with(normalize-space(),'Text to Trim')] //td[starts-with(normalize-space(text()),' Text to Trim ')] The second option is better as it targets at the specific nodes More string functions in XPATH: Functions Description starts-with( string1 ,  string2 ) Returns true if the first string starts with the second string. contains( string1 ,  string2 ) Returns true if the first string contains the second string. substring( string offset length ) Returns a section of the string. The section starts at  offset (which is a number), and is as long as the value provided at  length. substring-before( string1 ,  string2 ) Returns the part of  string1  up unti
Read more