jsspec - Project Hosting on Google Code

Older Nov 11, 2009 issue 18 (Move to GitHub) reported by thomas.42 - Current forks and contributions are happening over at GitHub. I recommend moving the official project there also. http://github.com/osteele/jsspec is the main JSSpec clone on GitHub Current forks and contributions are happening over at GitHub. I recommend moving the official project there also. http://github.com/osteele/jsspec is the main JSSpec clone on GitHub Oct 13, 2009 r148 ([No log message]) committed by jania902 - [No log message] [No log message] Sep 15, 2009 issue 17 ("title is undefined" javascript error. ) reported by yuviliom - What steps will reproduce the problem? 1. Tried to run the example case (found here: http://jania.pe.kr/aw/moin.cgi/JSSpec/UserGuide ) 2. Created the files as it said in the UserGuide wikidoc and browsed to the html file. 3. What is the expected output? What do you see instead? I expect the green horizontal line indicating all tests passed. I see instead a firebug error ("title is undefined JSSpec.js (line 543)") shown in jsspec_H3_error.png attached to this ticket. What version of the product are you using? On what operating system? using jsspec version: JSSpec20080923.zip On Ubuntu 9.04 linux with firefox: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090803 Ubuntu/9.04 (jaunty) Shiretoko/3.5.2 Please provide any additional information below. I think it's because of the capitalized H in "H3" leading to a null element. Lowering it to lowercase "h" seems to fix the issue. I have also attached a patch reflecting this change: JSSpec20080923_H3_errorfix.patch What steps will reproduce the problem? 1. Tried to run the example case (found here: http://jania.pe.kr/aw/moin.cgi/JSSpec/UserGuide ) 2. Created the files as it said in the UserGuide wikidoc and browsed to the html file. 3. What is the expected output? What do you see instead? I expect the green horizontal line indicating all tests passed. I see instead a firebug error ("title is undefined JSSpec.js (line 543)") shown in jsspec_H3_error.png attached to this ticket. What version of the product are you using? On what operating system? using jsspec version: JSSpec20080923.zip On Ubuntu 9.04 linux with firefox: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.2) Gecko/20090803 Ubuntu/9.04 (jaunty) Shiretoko/3.5.2 Please provide any additional information below. I think it's because of the capitalized H in "H3" leading to a null element. Lowering it to lowercase "h" seems to fix the issue. I have also attached a patch reflecting this change: JSSpec20080923_H3_errorfix.patch Apr 25, 2009 issue 10 (should_not_include fails with arrays) commented on by Classicist - Sorry for the typo in the above workaround, it should be: 'should not include X': function() { value_of([1, 2, 3].indexOf(4) == -1).should_be_true; // < = # workaround } Sorry for the typo in the above workaround, it should be: 'should not include X': function() { value_of([1, 2, 3].indexOf(4) == -1).should_be_true; // < = # workaround } Apr 25, 2009 issue 10 (should_not_include fails with arrays) commented on by Classicist - The above workaround causes an error on: JSSpec20080107.zip OSX, Leopard Firefox 3.0.9 A better workaround is: 'should not include X': function() { !value_of([1, 2, 3]).should_include(2); } The above workaround causes an error on: JSSpec20080107.zip OSX, Leopard Firefox 3.0.9 A better workaround is: 'should not include X': function() { !value_of([1, 2, 3]).should_include(2); } Feb 05, 2009 issue 16 (Safari/Webkit: Running file with no specs causes error and f...) reported by ckponnappa - What steps will reproduce the problem? 1. Create an empty spec like so: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="ko"> <head> <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/> <title>JSSpec results</title> <link rel="stylesheet" type="text/css" href="../../stylesheets/JSSpec.css"/> <link rel="stylesheet" type="text/css" href="../../stylesheets/dns_webapp.css"/> <script type="text/javascript" src="../diff_match_patch.js"></script> <script type="text/javascript" src="../JSSpec.js"></script> </head> <body> <div id="debug"></div> <script type="text/javascript">// <![CDATA[ // ]]> </script> </body> </html> Run this in Safari/Webkit, there is no output. In Webkit, click inspect element - this will show the following js error: TypeError: Result of expression 'document.getElementById('list')' [null] is not an object. Notes: I came across this because a parse error in my js code was causing JSSpec to also fail to detect any specs and enter the else branch on window.onload on line 1542 of JSSpec.js. A simple fix is to add a null check around 'document.getElementById('list')' - however, the real question is even if there were no specs why did onRunnerStart() fail to be invoked. What steps will reproduce the problem? 1. Create an empty spec like so: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="ko"> <head> <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/> <title>JSSpec results</title> <link rel="stylesheet" type="text/css" href="../../stylesheets/JSSpec.css"/> <link rel="stylesheet" type="text/css" href="../../stylesheets/dns_webapp.css"/> <script type="text/javascript" src="../diff_match_patch.js"></script> <script type="text/javascript" src="../JSSpec.js"></script> </head> <body> <div id="debug"></div> <script type="text/javascript">// <![CDATA[ // ]]> </script> </body> </html> Run this in Safari/Webkit, there is no output. In Webkit, click inspect element - this will show the following js error: TypeError: Result of expression 'document.getElementById('list')' [null] is not an object. Notes: I came across this because a parse error in my js code was causing JSSpec to also fail to detect any specs and enter the else branch on window.onload on line 1542 of JSSpec.js. A simple fix is to add a null check around 'document.getElementById('list')' - however, the real question is even if there were no specs why did onRunnerStart() fail to be invoked. Feb 04, 2009 issue 15 (Usability: Submitting patch to allow example names to be sho...) commented on by ckponnappa - Ok, this patch is intended to make the report look more like textmates rspec output - the entire spec isn't collapsed just the pre tags containing the code. This leaves the titles of the spec visible. I can add more to allow toggling on click etc. if you want me to. Ok, this patch is intended to make the report look more like textmates rspec output - the entire spec isn't collapsed just the pre tags containing the code. This leaves the titles of the spec visible. I can add more to allow toggling on click etc. if you want me to. Feb 04, 2009 issue 15 (Usability: Submitting patch to allow example names to be sho...) reported by ckponnappa - Diffed against trunk/v1/JSSpec.js revision 147 Sorry about the brief description, I wrote a detailed report earlier but Google Code blew up and I lost it - and now I need to rush :) Diffed against trunk/v1/JSSpec.js revision 147 Sorry about the brief description, I wrote a detailed report earlier but Google Code blew up and I lost it - and now I need to rush :) Jan 31, 2009 issue 14 (Pending status for test) commented on by tbrackley - This is an enhancement. Sorry I can't set the type. This is an enhancement. Sorry I can't set the type. Jan 31, 2009 issue 14 (Pending status for test) reported by tbrackley - This is an enhancement request. Can we have a "pending" test that neither fails (red) nor passes (green) but has the status of pending (yellow) which means though that the overall set of tests don't fail. This feature is implemented in storyq (BDD for .Net). This is useful when writing acceptance tests. The syntax of a test may look like: 'Mark a task as done click on the dash handle': function(){ value_of(this).is_pending } The output format would be yellow in the results. This is an enhancement request. Can we have a "pending" test that neither fails (red) nor passes (green) but has the status of pending (yellow) which means though that the overall set of tests don't fail. This feature is implemented in storyq (BDD for .Net). This is useful when writing acceptance tests. The syntax of a test may look like: 'Mark a task as done click on the dash handle': function(){ value_of(this).is_pending } The output format would be yellow in the results. Dec 24, 2008 r147 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 24, 2008 r146 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 23, 2008 r145 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 22, 2008 r144 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 22, 2008 r143 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 09, 2008 issue 12 (Feature Request: Adobe AIR) reported by thynctank - Somehow allow running of JSSpec in Adobe AIR. Allow loading/running of tests from within an Adobe AIR application. Somehow allow running of JSSpec in Adobe AIR. Allow loading/running of tests from within an Adobe AIR application. Dec 09, 2008 r142 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 06, 2008 r141 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 06, 2008 jsspec2_20081207.tar.gz (Experimental version of JSSpec which supports Rhino and Wind...) file uploaded by jania902 Dec 06, 2008 r140 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 06, 2008 r139 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 06, 2008 r138 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r137 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r136 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r135 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r134 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r133 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r132 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r131 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r130 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r129 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r128 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r127 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r126 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r125 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r124 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r123 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r122 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r121 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r120 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 05, 2008 r119 ([jsspec2] Implemented jsspec.Matcher for all types) committed by jania902 - [jsspec2] Implemented jsspec.Matcher for all types [jsspec2] Implemented jsspec.Matcher for all types Dec 05, 2008 r118 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 04, 2008 r117 ([jsspec2] Added summary) committed by jania902 - [jsspec2] Added summary [jsspec2] Added summary Dec 04, 2008 r116 (Added support for Windows Scripting Host) committed by jania902 - Added support for Windows Scripting Host Added support for Windows Scripting Host Dec 04, 2008 r115 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 04, 2008 r114 ([No log message]) committed by jania902 - [No log message] [No log message] Dec 04, 2008 r113 ([No log message]) committed by jania902 - [No log message] [No log message] Oct 31, 2008 r112 ([No log message]) committed by jania902 - [No log message] [No log message] Oct 28, 2008 r111 ([No log message]) committed by jania902 - [No log message] [No log message] Oct 27, 2008 issue 10 (should_not_include fails with arrays) commented on by matts.possiamo - This error also exists on: JSSpec20080107.zip OSX, Tiger Firefox 3.0.3 Workaround: function () { value_of([1, 2, 3].include(4)).should_be(false); } This error also exists on: JSSpec20080107.zip OSX, Tiger Firefox 3.0.3 Workaround: function () { value_of([1, 2, 3].include(4)).should_be(false); }

issue 16 (Safari/Webkit: Running file with no specs causes error and f...) reported by ckponnappa - What steps will reproduce the problem? 1. Create an empty spec like so: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="ko"> <head> <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/> <title>JSSpec results</title> <link rel="stylesheet" type="text/css" href="../../stylesheets/JSSpec.css"/> <link rel="stylesheet" type="text/css" href="../../stylesheets/dns_webapp.css"/> <script type="text/javascript" src="../diff_match_patch.js"></script> <script type="text/javascript" src="../JSSpec.js"></script> </head> <body> <div id="debug"></div> <script type="text/javascript">// <![CDATA[ // ]]> </script> </body> </html> Run this in Safari/Webkit, there is no output. In Webkit, click inspect element - this will show the following js error: TypeError: Result of expression 'document.getElementById('list')' [null] is not an object. Notes: I came across this because a parse error in my js code was causing JSSpec to also fail to detect any specs and enter the else branch on window.onload on line 1542 of JSSpec.js. A simple fix is to add a null check around 'document.getElementById('list')' - however, the real question is even if there were no specs why did onRunnerStart() fail to be invoked.

What steps will reproduce the problem? 1. Create an empty spec like so: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="ko"> <head> <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/> <title>JSSpec results</title> <link rel="stylesheet" type="text/css" href="../../stylesheets/JSSpec.css"/> <link rel="stylesheet" type="text/css" href="../../stylesheets/dns_webapp.css"/> <script type="text/javascript" src="../diff_match_patch.js"></script> <script type="text/javascript" src="../JSSpec.js"></script> </head> <body> <div id="debug"></div> <script type="text/javascript">// <![CDATA[ // ]]> </script> </body> </html> Run this in Safari/Webkit, there is no output. In Webkit, click inspect element - this will show the following js error: TypeError: Result of expression 'document.getElementById('list')' [null] is not an object. Notes: I came across this because a parse error in my js code was causing JSSpec to also fail to detect any specs and enter the else branch on window.onload on line 1542 of JSSpec.js. A simple fix is to add a null check around 'document.getElementById('list')' - however, the real question is even if there were no specs why did onRunnerStart() fail to be invoked.

Older