jQuery Reel Test Suite

Reel is very well tested. To date we have 1727 tests in 331 tasks and 11 modules. Between releases (1.2 and 1.2.1), the unit test coverage has been increased by 45% with 99% of code being covered now. The suite will keep on growing as enhancements are made or new bugs discovered. The test suite grows independent on regular version releases.

Usage?

Launch index.html in your browser or visit http://test.vostrel.cz/jquery.reel/test

Positive Results

Both manual and automated tests indicate, that Reel is extremely compatible with nearly everything. From an array of 12 browsers Reel fails badly in just two cases, in mobile Opera Mini (see FAQ for explanation) and on Windows Phones. I could as well leave out these browsers completely to make it seem Reel is 100% compatible, but let's leave them there to be fair.

Desktop

Chrome

• Mozilla/5.0 (Windows; U; Windows NT 5.1) AppleWebKit/533.4 Chrome/5.0.375.125 Safari/533.4
  • OK -- Unit
  • OK -- Interaction
• Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_5) AppleWebKit/534.16 Chrome/10.0.648.205 Safari/534.16
  • OK -- Unit
  • OK -- Interaction

Firefox

• Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0.1) Gecko/20100101 Firefox/8.0.1
  • OK -- Unit
  • OK -- Interaction
• Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; rv:1.9.2.16) Gecko/20110319 Firefox/3.6.16
  • OK -- Unit
  • OK -- Interaction

Internet Explorer

• Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0; SLCC2; Media Center PC 6.0)
  • OK -- Unit
  • OK -- Interaction
• Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; Media Center PC 6.0)
  • OK -- Unit
  • OK -- Interaction
• Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)
  • OK -- Unit
  • OK -- Interaction
• Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
  • OK -- Unit
  • OK -- Interaction

Safari / WebKit

• Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/535.6+ (KHTML, like Gecko) Version/5.1 Safari/534.50
  • OK -- Unit
  • OK -- Interaction
• Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.50 (KHTML, like Gecko) Version/5.1 Safari/534.50
  • OK -- Unit
  • OK -- Interaction

Opera

• Opera/9.80 (Macintosh; Intel Mac OS X; U; en) Presto/2.2.15 Version/10.10
  • OK -- Unit
  • OK -- Interaction

Camino

• Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; rv:1.9.0.19) Gecko/2010111021 Camino/2.0.6
  • OK -- Unit
  • OK -- Interaction

Mobile

iOS Safari

• Mozilla/5.0 (iPad; U; CPU OS 4_2_1 like Mac OS X) AppleWebKit/533.17.9 Version/5.0.2 Mobile/8C148 Safari/6533.18.5
  • OK -- Unit
  • OK -- Interaction
• Mozilla/5.0 (iPhone Simulator; U; CPU iPhone OS 3_0) AppleWebKit/528.18 Version/4.0 Mobile/7A341 Safari/528.16
  • OK -- Unit
  • OK -- Interaction

Android WebKit

• Mozilla/5.0 (Linux; U; Android 2.3.5; ZTE-SKATE) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1
  • OK -- Unit
  • OK -- Interaction

Opera Mobile

• Opera/9.80 (Macintosh; Intel Mac OS X; Opera Mobi/27; U) Presto/2.4.18 Version/10.00
  • OK -- Unit
  • FAIL -- Interaction

Opera Mini

• Opera/9.80 (J2ME/MIDP; Opera Mini/5.0.18697/19.892; U) Presto/2.5.25
  • FAIL -- Unit
  • FAIL -- Interaction
  • See FAQ for information why this particular "browser" fails

Fennec

• Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; rv:1.9.1b2pre) Gecko/20081015 Fennec/1.0a1
  • OK -- Unit
  • FAIL -- Interaction

Windows Mobile

• Mozilla/5.0 (???)
  • ? -- Unit
  • FAIL -- Interaction

Missing some?

Do you have a test suite run result not listed here? Send it to me (Petr Vostřel) along with the signature found at the top of the QUnit test page. I will happily add it here. Or you can always fork the project and commit the updated file.

Results Reporting

In 1.1 I asked you to submit failing tests reports to me. You did and it helped me tremendously. I thank you very much for doing so!

In 1.2 the report gathering and submission is fully automated, so you don't need to do a thing to help. You take part in the distributed testing efforts merely by running the tests. Run the tests on as many different devices as you can (even exotic ones) to help me even more.

After each test run finishes, its anonymous results are then automatically submitted on-line for collection and analysis. The report contains this:

    {
      timestamp:  "1325202485687",
      filter:     [
        // Listed filtered modules (if any)
      ],
      count: {
        total:    655,
        pass:     655,
        fail:     0
      },
      fails:      [
        // List of all failing tests
      ],
      version: {
        jquery:   "1.7.1",
        reel:     "1.2"
      },
      host:       "jquery.vostrel.cz", // This would be your domain name
      results:    "Tests completed in 44106 milliseconds. 655 tests of 655 passed, 0 failed.",
      agent:      "Mozilla/5.0 (Windows NT 6.1) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7"
    }