gecko/testing/release/minotaur
2008-04-11 16:04:24 -07:00
..
checkBookmarks.py bug 416049 Minotaur needs better output r=alice 2008-03-04 14:52:05 -08:00
checkReleaseChannel.py bug 401170 New Changes for Minotaur test tool reviewer: bhearsum 2008-01-07 16:54:00 -08:00
diffBookmarks.py bug 416049 Minotaur needs better output r=alice 2008-03-04 14:52:05 -08:00
getOsInfo.py bug 401170 New Changes for Minotaur test tool reviewer: bhearsum 2008-01-07 16:54:00 -08:00
grabEULA.sh bug 401170 New Changes for Minotaur test tool reviewer: bhearsum 2008-01-07 16:54:00 -08:00
installdmg-expect.ex bug 424253 Minotaur cleanup patch r=robcee 2008-03-27 09:49:02 -07:00
installdmg.sh bug 424253 Minotaur cleanup patch r=robcee 2008-03-27 09:49:02 -07:00
logAppender.py bug 416049 Minotaur needs better output r=alice 2008-03-04 14:52:05 -08:00
minotaur.sh bug 414056 Allow Minotaur to run back to back r=alice 2008-03-04 15:16:55 -08:00
minotaur.xul bug 401170 New Changes for Minotaur test tool reviewer: bhearsum 2008-01-07 16:54:00 -08:00
mozDownload.py bug 424253 Minotaur cleanup patch r=robcee 2008-03-27 09:49:02 -07:00
mozInstall.py bug 424253 Minotaur cleanup patch r=robcee 2008-03-27 09:49:02 -07:00
partner.py bug 416049 Minotaur needs better output r=alice 2008-03-04 14:52:05 -08:00
quit.js Bug 385987 - initial check in of minotaur tool r=robcee 2007-09-13 20:28:15 -07:00
quit.xul bug 414056 Allow Minotaur to run back to back r=alice 2008-03-04 15:16:55 -08:00
README.txt bug 401170 New Changes for Minotaur test tool reviewer: bhearsum 2008-01-07 16:54:00 -08:00
run-minotaur.py bug 424253 Minotaur cleanup patch r=robcee 2008-03-27 09:49:02 -07:00
sb.js bug 396132 Minotaur needs to check protocol handlers r=rcampbell 2008-04-11 16:04:24 -07:00
tests.manifest bug 401170 New Changes for Minotaur test tool reviewer: bhearsum 2008-01-07 16:54:00 -08:00
user.js bug 414056 Allow Minotaur to run back to back r=alice 2008-03-04 15:16:55 -08:00

 == Steps to Install Minotaur ==
 1. Drop all the Minotaur files into a directory - this is the MINOTAUR_DIR folder
 2. Change the tests.manifest file to also point to this directory
    DO NOT FORGET TRAILING SLASH!!:
    Windows: content minotaur file:///c:/code/minotaur/
    Mac/Linux: content minotaur file:///Users/clint/code/Minotaur/workspace/
 3. If you will be using mozDownload.py - ensure that wget is installed!
 4. Run Minotaur - run it without commands to get a usage statement
 5. Run Minotaur - results will be in <buildname>/<version>/<locale> directory in the
    MINOTAUR_DIR folder

 == To get verification files for a first run of a build ==
 1. Run Minotaur without the "verification" args, this means without -b -o and
    -c options
 2. The output.xml and bookmarks.html will be placed in <buildname>/<version>/<locale>
    directory in the MINOTAUR_DIR folder
 3. View the http.log that was generated (or partner specs) and create a
    release.txt file where the first (and only) line is the release channel name
 4. Edit these files if needed, and copy them to a verification directory.
 5. Run Minotaur again with using these as your verification files for the
    -b -o and -c options
 6. Submit those files for review and check-in so that future runs will use
    those files to diff against.

== Known Issues and Troubleshooting ==
* No Firefox windows appear when I run Minotaur, and the Firefox process (may)
  hang out in the system process list after the test finishes:  If you see this
  then Firefox is trying to tell you that your tests.manifest file is messed up.
  Either it has the wrong path, or you forgot the trailing slash.

* On Mac, you should use the following style paths:
<path to firefox.app>/Contents/MacOS This is the proper -f parameter path for a
mac.  So, for example, if firefox is installed in applications, this becomes:
/Applications/Firefox.app/Contents/MacOS/