I updated the DOM Test Suite
to use the latest JsUnit and reran the full set of tests to determine
which assertions are still being fired.

The test results are nothing new from what I can tell and are probably already included in the mochikit
version of the DOM Test suite. The assertions are relatively minor and known.

• Assertion Count

• Test Results with rough location of assertions

Yesterday, Pratap Lakshman of Microsoft announced the publication of the first draft of “JScript Deviations from ES3″

The document covers not only JScript as implemented in IE, but JavaScript as implemented in Firefox, Opera and Safari. This should make for some interesting reading!

Thanks Pratap!

Assert This! - Top Site Assertions, October 27, 2007

No matter where you go, Jesse’s been there already.

During some top site testing of about 7,500 pages with a debug Minefield build on Linux over the weekend, I ran into the following assertions ordered by decreasing count. This should give some idea of the frequency of each in the wild.

My shell account at Dreamhost was compromised and this site was vandalized. It appears this was a wide spread event and a number of other sites hosted at Dreamhost were affected. If you have an account at Dreamhost, I recommend you change your passwords for your shell and email and check your web content for modifications.

I’ve cleaned up the mess (I think). Although as far as I can tell the Spider.xpi was not modified, I have generated a new version of Spider 0.0.2.7 to force an update to any Spider users.

The latest installment of my automated testing saga is now available at Script Framework. This outlines the components that I have been using in automated testing and provides an example where a build is downloaded, installed, a profile created, an extension installed and a simple test that the extension works is performed.

Benjamin Smedberg wrote to point out killableprocess.py which looks like a much more robust tool than timed_run.py. I’ll check it out as a replacement for timed_run.py in my framework as soon as I finish the first round of documentation I have been supposed to write about my test framework since … like … forever.

timed_run.py is a modified version of a Python script written by Chris Cooper that manages the execution of external programs with the ability to terminate programs which do not complete within a specified period of time.

Spider has been updated to version 0.0.2.4. This update includes minor changes to the default output messages Spider issues as well as the ability to load browser chrome in addition to normal web pages. I’ve made a kludgey attempt to automate Firefox which simultaneously illustrates the possibilities and pitfalls of this approach. If you are a XUL hacker and have suggestions on how to improve this approach, I would really appreciate your feedback.

/bc

DANGER! Will Robinson! DANGER!

If you are not comfortable using beta software, do not know how to back up your profile or don’t know what bugzilla is, then please do not download nightly builds for testing!

Every little bit helps…

One of the strengths of the Mozilla community which has helped make Firefox such a success are the people who love Firefox who also help to make it better. Many people have filed bugs on issues they have discovered and I would like to ask those people for a little bit of help.

Mozilla developers have been working hard to fix bugs for the releases of Firefox 2 and Thunderbird 2 later this year. So far, there have been 3331 bugs fixed on the 1.8 branch from which Firefox 2 and Thunderbird 2 will be released. Unfortunately, only 341 have been verified as fixed so far.

Crashes and Hangs

211 bugs which cause crashes or hangs have been fixed but not verified.

Regressions

327 bugs which cause regressions have been fixed but not verified.

If you filed one of the bugs on these lists, it would be very helpful if you could download a nightly build of Firefox 2 or Thunderbird 2 and verify that the bug you filed is actually fixed. Please comment in the bug and add me (bclary at bclary dot com) to the cc list.

Tip: You can easily find the bugs you filed by clicking on one of the above links and after the query loads, clicking the “Edit Search” link at the bottom of the page. Then under Email and Numbering, click the reporter check box under Any of of: and add your bugzilla email address to the field below the contains select box.

Thanks to Brian J Polidoro for bringing this to my attention.

Better now than never!

If you are a developer for a commercial web site or web application and Firefox compatibility is important to you, your employer and your customers, please begin testing your content and applications with the nightly builds of Firefox 2! The code is very quickly being locked down so that it is becoming increasingly difficult to get changes made before the release of Firefox 2. If you don’t report a problem with your site or application soon, it may be impossible to get the fix into the next release. The most important things to look for are regressions where something that worked in Firefox 1.5 is now broken in Firefox 2. This month marks the sixth year I have been a member of the Mozilla Community and it has never failed that someone from a major web site or application developer waits until the last minute to test their content with the upcoming release. Don’t be the grasshopper! Test today not tomorrow!

The problem

In bash, running test programs which indicate their pass or fail status via an exit code can be problematic when they are run as part of a pipeline in Linux, Mac OS X or Cygwin since the reported exit code of a pipeline is normally the exit code of the last program in the pipeline. If the test program is not the last program in the pipeline, then its exit code will be hidden by the exit code of the last program.

The solution

bash version 3 introduced an option which changes the exit code behavior of pipelines and reports the exit code of the pipeline as the exit code of the last program to return a non-zero exit code. So long as none of the programs following the test program report a non-zero exit code, the pipeline will report its exit code to be that of the test program. To enable this option, simply execute:

set -o pipefail

in the shell where the test program will execute.

Caveat Emptor

The pipefail option was introduced in bash version 3 which is supported in current Linux and Cygwin releases of bash but is not supported by the default bash shipped on Mac OS X.

To work around this lagging version on Mac OS X, you can simply download, build and install the latest version of bash from http://ftp.gnu.org/gnu/bash/ into your /usr/local/bin directory. Then code your shell scripts to use the shebang !#/usr/local/bin/bash instead of the normal /bin/bash. For systems such as Linux or Cygwin which already provide a pipefail capable version of bash, simply create a hard link from /usr/local/bin/bash to the system version /bin/bash.

ln /bin/bash /usr/local/bin/bash