[Proto-Scripty] Re: Trying to develop something new
2009/4/1 kangax : > > > > On Mar 31, 11:54 am, Richard Quadling > wrote: > [...] >> Including the browser resize ones? How did you get them to pass? > > Nope. Those still fail, of course. Those are not Prototype bugs after > all - rather, browser limitation : ) > > -- > kangax > > > Thank you. -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Trying to develop something new
On Mar 31, 11:54 am, Richard Quadling wrote: [...] > Including the browser resize ones? How did you get them to pass? Nope. Those still fail, of course. Those are not Prototype bugs after all - rather, browser limitation : ) -- kangax --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Trying to develop something new
2009/3/30 kangax : > > On Mar 30, 5:54 am, "T.J. Crowder" wrote: >> Hi, >> >> > All tests pass here in Chrome with RC1. >> >> Chrome 1 or Chrome 2? > > Both. > > [...] > > -- > kangax > > > Including the browser resize ones? How did you get them to pass? -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Trying to develop something new
On Mar 30, 5:54 am, "T.J. Crowder" wrote: > Hi, > > > All tests pass here in Chrome with RC1. > > Chrome 1 or Chrome 2? Both. [...] -- kangax --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Trying to develop something new
Hi, > All tests pass here in Chrome with RC1. Chrome 1 or Chrome 2? -- T.J. :-) On Mar 29, 8:18 pm, kangax wrote: > On Mar 29, 4:38 am, "T.J. Crowder" wrote: > > > Hi Richard, > > > FYI, I happen to know that kangax was working on Chrome support and I > > believe a couple of days ago he got a clean slate on Chrome 2. I > > don't know whether there's a plan to support Chrome 1 or not. But > > progress definitely being made. > > Chrome support is a must. Its share, by now, is more than that of > Opera (afaik). All tests pass here in Chrome with RC1. If anyone finds > a problem, let us know. Otherwise, we should update supported browsers > page to include Chrome support (as of 1.6.1RC1) > > [...] > > -- > kangax --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Trying to develop something new
On Mar 29, 4:38 am, "T.J. Crowder" wrote: > Hi Richard, > > FYI, I happen to know that kangax was working on Chrome support and I > believe a couple of days ago he got a clean slate on Chrome 2. I > don't know whether there's a plan to support Chrome 1 or not. But > progress definitely being made. Chrome support is a must. Its share, by now, is more than that of Opera (afaik). All tests pass here in Chrome with RC1. If anyone finds a problem, let us know. Otherwise, we should update supported browsers page to include Chrome support (as of 1.6.1RC1) [...] -- kangax --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Trying to develop something new
Thank you very much for your help, I did as you said and made it run. I had some more path issues for opera and chrome, mostly because of my italian edition of windows xp, but from your suggestions it was easy to find my way out. Now I'm all set and starting playing around with prototype. Luca --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Trying to develop something new
Hi Richard, FYI, I happen to know that kangax was working on Chrome support and I believe a couple of days ago he got a clean slate on Chrome 2. I don't know whether there's a plan to support Chrome 1 or not. But progress definitely being made. -- T.J. :-) On Mar 27, 5:32 pm, Richard Quadling wrote: > 2009/3/27 T.J. Crowder : > > > > > > > Hi Luca, > > > Curiously enough, I ran into both of those issues the other day. > > >> The point is I don't get any html files in test/unit! > > > That's because the contribute page[1] is wrong about that. The HTML > > files aren't in test/unit (they're in test/unit/tmp), and they aren't > > *anywhere* until after you've run rake test, because they're generated > > at that point, not at the point they're mentioned on the contribute > > page (just after rake dist). There's an open ticket in Lighthouse to > > correct that. > > > [1]http://prototypejs.org/contribute > > >> As Tobie suggested I tried to rake test and all I got is a persistent > >> "Started tests in Chrome" line with no cpu workload at all > > > I'm guessing you're using Windows. This happens because of a bug (or, > > arguably, two bugs) in the unit testing stuff; I've mentioned it to > > Tobie but haven't had time to find out what project it's in (I think > > it's unittest_js, which is one of the submodules) and raise a formal > > ticket or two. The problem is that it's looking in the wrong place > > for Chrome, not finding it, and apparently going off into never-never > > land. You can fix it by doing this in your command window just before > > rake test: > > > set UserPath=%UserProfile% > > > Alternately you can edit line #6 in vendor/unittest_js/lib/unittest_js/ > > browsers/chrome.rb > > > ENV['UserPath'] || "C:/Documents and Settings/Administrator", > > > to read > > > ENV['UserPath'] || ENV['UserProfile'] || "C:/Documents and Settings/ > > Administrator", > > > Here are some further notes from what testing I've done so far (which > > is quite limited): > > > 1. You will also probably want to use the BROWSERS option of rake > > test, which lets you decide which browsers to run the tests in: The > > options I've found so far are chrome, ie, firefox, opera, and safari > > (which probably covers it, for now). It's a comma-delimited list. So > > for instance, this runs the tests in Firefox only: > > > rake test BROWSERS=firefox > > > or perhaps you want to test chrome and IE: > > > rake test BROWSERS=chrome,ie > > > 2. Always have the browser you want to test running before you run > > rake test. It's *supposed* to launch the browser, but I've had a lot > > of trouble with that under Windows. > > > 3. When testing Opera, Rake test will display a "major pain under > > windows" message saying that you have to close the Opera window after > > each unit test. I find that if I have Opera running before I start > > the test, I don't _usually_ have to do that. I have had to sometimes, > > but not often. > > > HTH, > > -- > > T.J. Crowder > > tj / crowder software / com > > Independent Software Engineer, consulting services available > > > On Mar 26, 6:14 pm, Luca Diracca wrote: > >> Hi all, > >> I started this topic in lighthouse and moved here under suggestion of > >> Tobie. > > >> I'm pretty sure I'm overviewing something embarassingly obvious but > >> I'm trying to modify some code and, to do it properly, I'm trying to > >> download the entire unit test suit through git. > > >> git clone, git submodule init, git submodule update, rake dist OK. > > >> The point is I don't get any html files in test/unit! I also tried to > >> download the tarball but I didn't have any more luck, neither I did > >> browsing the web tree. > > >> As Tobie suggested I tried to rake test and all I got is a persistent > >> "Started tests in Chrome" line with no cpu workload at all > > >> I've got a just-installed ruby 1.8.6 - 26 and a just-installed git > >> 1.6.2 > > >> What am I missing? > > >> Thanks in advance Luca > > Thank you for this. Tested Chrome. Got 3 failures in Chrome (all in > dom_test - 2 in testViewportDimensions and 1 in > testViewportScrollOffsets) > > 0 assertions, 2 failures, 0 errors > Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR > THIS TEST TO PASS > expected: <1314>, actual: <1264> > Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR > THIS TEST TO PASS > expected: <903>, actual: <853> > > and > > 2 assertions, 1 failures, 0 errors > Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR > THESE TESTS TO PASS > expected: <25>, actual: <0> > > And 2 failures in IE related to (selector_test - both in > testSelectorWithEmpty). > > 0 assertions, 2 failures, 0 errors > Failure: #level1 *:empty > expected: <[, , id="level2_3">]>, actual: <[, id="level3_2">, , ]> > Failure: newlines count as content! > expected: <[]>, actual: <[]> > > Tested using 6c38d84 > > -- > - > Richard Quadling > Zend Certified Engineer :http://zend.com/zce.ph
[Proto-Scripty] Re: Trying to develop something new
2009/3/27 T.J. Crowder : > > Hi Luca, > > Curiously enough, I ran into both of those issues the other day. > >> The point is I don't get any html files in test/unit! > > That's because the contribute page[1] is wrong about that. The HTML > files aren't in test/unit (they're in test/unit/tmp), and they aren't > *anywhere* until after you've run rake test, because they're generated > at that point, not at the point they're mentioned on the contribute > page (just after rake dist). There's an open ticket in Lighthouse to > correct that. > > [1] http://prototypejs.org/contribute > >> As Tobie suggested I tried to rake test and all I got is a persistent >> "Started tests in Chrome" line with no cpu workload at all > > I'm guessing you're using Windows. This happens because of a bug (or, > arguably, two bugs) in the unit testing stuff; I've mentioned it to > Tobie but haven't had time to find out what project it's in (I think > it's unittest_js, which is one of the submodules) and raise a formal > ticket or two. The problem is that it's looking in the wrong place > for Chrome, not finding it, and apparently going off into never-never > land. You can fix it by doing this in your command window just before > rake test: > > set UserPath=%UserProfile% > > Alternately you can edit line #6 in vendor/unittest_js/lib/unittest_js/ > browsers/chrome.rb > > ENV['UserPath'] || "C:/Documents and Settings/Administrator", > > to read > > ENV['UserPath'] || ENV['UserProfile'] || "C:/Documents and Settings/ > Administrator", > > Here are some further notes from what testing I've done so far (which > is quite limited): > > 1. You will also probably want to use the BROWSERS option of rake > test, which lets you decide which browsers to run the tests in: The > options I've found so far are chrome, ie, firefox, opera, and safari > (which probably covers it, for now). It's a comma-delimited list. So > for instance, this runs the tests in Firefox only: > > rake test BROWSERS=firefox > > or perhaps you want to test chrome and IE: > > rake test BROWSERS=chrome,ie > > 2. Always have the browser you want to test running before you run > rake test. It's *supposed* to launch the browser, but I've had a lot > of trouble with that under Windows. > > 3. When testing Opera, Rake test will display a "major pain under > windows" message saying that you have to close the Opera window after > each unit test. I find that if I have Opera running before I start > the test, I don't _usually_ have to do that. I have had to sometimes, > but not often. > > HTH, > -- > T.J. Crowder > tj / crowder software / com > Independent Software Engineer, consulting services available > > > On Mar 26, 6:14 pm, Luca Diracca wrote: >> Hi all, >> I started this topic in lighthouse and moved here under suggestion of >> Tobie. >> >> I'm pretty sure I'm overviewing something embarassingly obvious but >> I'm trying to modify some code and, to do it properly, I'm trying to >> download the entire unit test suit through git. >> >> git clone, git submodule init, git submodule update, rake dist OK. >> >> The point is I don't get any html files in test/unit! I also tried to >> download the tarball but I didn't have any more luck, neither I did >> browsing the web tree. >> >> As Tobie suggested I tried to rake test and all I got is a persistent >> "Started tests in Chrome" line with no cpu workload at all >> >> I've got a just-installed ruby 1.8.6 - 26 and a just-installed git >> 1.6.2 >> >> What am I missing? >> >> Thanks in advance Luca > > > Thank you for this. Tested Chrome. Got 3 failures in Chrome (all in dom_test - 2 in testViewportDimensions and 1 in testViewportScrollOffsets) 0 assertions, 2 failures, 0 errors Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR THIS TEST TO PASS expected: <1314>, actual: <1264> Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR THIS TEST TO PASS expected: <903>, actual: <853> and 2 assertions, 1 failures, 0 errors Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR THESE TESTS TO PASS expected: <25>, actual: <0> And 2 failures in IE related to (selector_test - both in testSelectorWithEmpty). 0 assertions, 2 failures, 0 errors Failure: #level1 *:empty expected: <[, , ]>, actual: <[, , , ]> Failure: newlines count as content! expected: <[]>, actual: <[]> Tested using 6c38d84 -- - Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=
[Proto-Scripty] Re: Trying to develop something new
Other available rake options are: TESTS and TESTCASES. The former let's you specify a comma-separated list of pages: $ rake test TESTS=array,string (builds and runs the tests found in array.js and string.js). The latter lets you specify actual TESTCASES: $ rake test TESTCASES=test$w,testArrayInject You can of course combine those. Best, Tobie On Mar 27, 4:01 pm, "T.J. Crowder" wrote: > Hi Luca, > > Curiously enough, I ran into both of those issues the other day. > > > The point is I don't get any html files in test/unit! > > That's because the contribute page[1] is wrong about that. The HTML > files aren't in test/unit (they're in test/unit/tmp), and they aren't > *anywhere* until after you've run rake test, because they're generated > at that point, not at the point they're mentioned on the contribute > page (just after rake dist). There's an open ticket in Lighthouse to > correct that. > > [1]http://prototypejs.org/contribute > > > As Tobie suggested I tried to rake test and all I got is a persistent > > "Started tests in Chrome" line with no cpu workload at all > > I'm guessing you're using Windows. This happens because of a bug (or, > arguably, two bugs) in the unit testing stuff; I've mentioned it to > Tobie but haven't had time to find out what project it's in (I think > it's unittest_js, which is one of the submodules) and raise a formal > ticket or two. The problem is that it's looking in the wrong place > for Chrome, not finding it, and apparently going off into never-never > land. You can fix it by doing this in your command window just before > rake test: > > set UserPath=%UserProfile% > > Alternately you can edit line #6 in vendor/unittest_js/lib/unittest_js/ > browsers/chrome.rb > > ENV['UserPath'] || "C:/Documents and Settings/Administrator", > > to read > > ENV['UserPath'] || ENV['UserProfile'] || "C:/Documents and Settings/ > Administrator", > > Here are some further notes from what testing I've done so far (which > is quite limited): > > 1. You will also probably want to use the BROWSERS option of rake > test, which lets you decide which browsers to run the tests in: The > options I've found so far are chrome, ie, firefox, opera, and safari > (which probably covers it, for now). It's a comma-delimited list. So > for instance, this runs the tests in Firefox only: > > rake test BROWSERS=firefox > > or perhaps you want to test chrome and IE: > > rake test BROWSERS=chrome,ie > > 2. Always have the browser you want to test running before you run > rake test. It's *supposed* to launch the browser, but I've had a lot > of trouble with that under Windows. > > 3. When testing Opera, Rake test will display a "major pain under > windows" message saying that you have to close the Opera window after > each unit test. I find that if I have Opera running before I start > the test, I don't _usually_ have to do that. I have had to sometimes, > but not often. > > HTH, > -- > T.J. Crowder > tj / crowder software / com > Independent Software Engineer, consulting services available > > On Mar 26, 6:14 pm, Luca Diracca wrote: > > > Hi all, > > I started this topic in lighthouse and moved here under suggestion of > > Tobie. > > > I'm pretty sure I'm overviewing something embarassingly obvious but > > I'm trying to modify some code and, to do it properly, I'm trying to > > download the entire unit test suit through git. > > > git clone, git submodule init, git submodule update, rake dist OK. > > > The point is I don't get any html files in test/unit! I also tried to > > download the tarball but I didn't have any more luck, neither I did > > browsing the web tree. > > > As Tobie suggested I tried to rake test and all I got is a persistent > > "Started tests in Chrome" line with no cpu workload at all > > > I've got a just-installed ruby 1.8.6 - 26 and a just-installed git > > 1.6.2 > > > What am I missing? > > > Thanks in advance Luca --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
[Proto-Scripty] Re: Trying to develop something new
Hi Luca, Curiously enough, I ran into both of those issues the other day. > The point is I don't get any html files in test/unit! That's because the contribute page[1] is wrong about that. The HTML files aren't in test/unit (they're in test/unit/tmp), and they aren't *anywhere* until after you've run rake test, because they're generated at that point, not at the point they're mentioned on the contribute page (just after rake dist). There's an open ticket in Lighthouse to correct that. [1] http://prototypejs.org/contribute > As Tobie suggested I tried to rake test and all I got is a persistent > "Started tests in Chrome" line with no cpu workload at all I'm guessing you're using Windows. This happens because of a bug (or, arguably, two bugs) in the unit testing stuff; I've mentioned it to Tobie but haven't had time to find out what project it's in (I think it's unittest_js, which is one of the submodules) and raise a formal ticket or two. The problem is that it's looking in the wrong place for Chrome, not finding it, and apparently going off into never-never land. You can fix it by doing this in your command window just before rake test: set UserPath=%UserProfile% Alternately you can edit line #6 in vendor/unittest_js/lib/unittest_js/ browsers/chrome.rb ENV['UserPath'] || "C:/Documents and Settings/Administrator", to read ENV['UserPath'] || ENV['UserProfile'] || "C:/Documents and Settings/ Administrator", Here are some further notes from what testing I've done so far (which is quite limited): 1. You will also probably want to use the BROWSERS option of rake test, which lets you decide which browsers to run the tests in: The options I've found so far are chrome, ie, firefox, opera, and safari (which probably covers it, for now). It's a comma-delimited list. So for instance, this runs the tests in Firefox only: rake test BROWSERS=firefox or perhaps you want to test chrome and IE: rake test BROWSERS=chrome,ie 2. Always have the browser you want to test running before you run rake test. It's *supposed* to launch the browser, but I've had a lot of trouble with that under Windows. 3. When testing Opera, Rake test will display a "major pain under windows" message saying that you have to close the Opera window after each unit test. I find that if I have Opera running before I start the test, I don't _usually_ have to do that. I have had to sometimes, but not often. HTH, -- T.J. Crowder tj / crowder software / com Independent Software Engineer, consulting services available On Mar 26, 6:14 pm, Luca Diracca wrote: > Hi all, > I started this topic in lighthouse and moved here under suggestion of > Tobie. > > I'm pretty sure I'm overviewing something embarassingly obvious but > I'm trying to modify some code and, to do it properly, I'm trying to > download the entire unit test suit through git. > > git clone, git submodule init, git submodule update, rake dist OK. > > The point is I don't get any html files in test/unit! I also tried to > download the tarball but I didn't have any more luck, neither I did > browsing the web tree. > > As Tobie suggested I tried to rake test and all I got is a persistent > "Started tests in Chrome" line with no cpu workload at all > > I've got a just-installed ruby 1.8.6 - 26 and a just-installed git > 1.6.2 > > What am I missing? > > Thanks in advance Luca --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To post to this group, send email to prototype-scriptaculous@googlegroups.com To unsubscribe from this group, send email to prototype-scriptaculous+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en -~--~~~~--~~--~--~---
