[Prototype-core] Re: Cloned repo via git, not seeing the unit test html files

2009-03-22 Thread Richard Quadling

2009/3/21 T.J. Crowder t...@crowdersoftware.com:

 Hi all,

 FWIW, my results for trunk this morning on Windows XP:

 * Fully passes on FF3

 * Tries to run against Chrome but fails to launch it (rake just sits
 there until you kill it); but then, Chrome isn't a supported browser
 [1], not sure why we're trying to test it

 * Failures on IE7:
form_test.html - testFormMethodsOnExtendedElements:
 4 assertions, 1 failures, 1 errors
 Failure: assert
 got undefined
 TypeError: Object doesn't support this property or method, error=
 ([object Error])
selector_test.html - testFormMethodsOnExtendedElements:
 0 assertions, 2 failures, 0 errors
 Failure: #level1 *:empty
 expected: [span id=level3_1, span id=level3_2, div
 id=level2_3], actual: [span id=level3_1, span
 id=level3_2, em id=level_only_child, div id=level2_3]
 Failure: newlines count as content!
 expected: [], actual: [em id=level_only_child]

 * Failures in Opera 9.64, all in dom_test.html:
 testElementScrollTo
 0 assertions, 2 failures, 0 errors
 Failure: assertEqual
 expected: 1946, actual: 0
 Failure: assertEqual
 expected: 1946, actual: 0
 testViewportDimensions
 0 assertions, 2 failures, 0 errors
 Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR
 THIS TEST TO PASS
 expected: 1041, actual: 991
 Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR
 THIS TEST TO PASS
 expected: 648, actual: 598
 testViewportScrollOffsets
 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

 (Yes, I do have JavaScript allowed to do anything it wants with the
 window.)

 * Refuses to test against Safari 3.2.2, says it's not supported on
 Windows

 [1] http://prototypejs.org/download

 FWIW,

 -- T.J. :-)

 On Mar 20, 8:59 pm, kangax kan...@gmail.com wrote:
 On Mar 20, 3:03 pm, T.J. Crowder t...@crowdersoftware.com wrote:

  Thanks, Tobie.  That was the missing bit all right.  The contribute
  page _does_ mention rake test, but much further down; I'll update
  the page to tie things together a bit.

  Out of curiousity, anyone successfully run the tests lately on Chrome,
  IE7, or Opera on Windows?

 I'm on mac. Trunk fully passes FF3 and Safari 4 here. There are a
 couple of failures in Opera 9.64. I'm taking care of IE8 at the moment
 - just pushed few fixes for DOM suite.

 [...]

 --
 kangax
 


I use Chrome and FF as my main browsers. Chrome as it is so clean. FF
because of FB. IE7 for testing. So far, my code is working as expected
on all 3 of these browsers.



-- 
-
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498r=213474731
Standing on the shoulders of some very clever giants!

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Cloned repo via git, not seeing the unit test html files

2009-03-21 Thread T.J. Crowder

Hi all,

FWIW, my results for trunk this morning on Windows XP:

* Fully passes on FF3

* Tries to run against Chrome but fails to launch it (rake just sits
there until you kill it); but then, Chrome isn't a supported browser
[1], not sure why we're trying to test it

* Failures on IE7:
form_test.html - testFormMethodsOnExtendedElements:
4 assertions, 1 failures, 1 errors
Failure: assert
got undefined
TypeError: Object doesn't support this property or method, error=
([object Error])
selector_test.html - testFormMethodsOnExtendedElements:
0 assertions, 2 failures, 0 errors
Failure: #level1 *:empty
expected: [span id=level3_1, span id=level3_2, div
id=level2_3], actual: [span id=level3_1, span
id=level3_2, em id=level_only_child, div id=level2_3]
Failure: newlines count as content!
expected: [], actual: [em id=level_only_child]

* Failures in Opera 9.64, all in dom_test.html:
 testElementScrollTo
0 assertions, 2 failures, 0 errors
Failure: assertEqual
expected: 1946, actual: 0
Failure: assertEqual
expected: 1946, actual: 0
 testViewportDimensions
0 assertions, 2 failures, 0 errors
Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR
THIS TEST TO PASS
expected: 1041, actual: 991
Failure: NOTE: YOU MUST ALLOW JAVASCRIPT TO RESIZE YOUR WINDOW FOR
THIS TEST TO PASS
expected: 648, actual: 598
 testViewportScrollOffsets
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

(Yes, I do have JavaScript allowed to do anything it wants with the
window.)

* Refuses to test against Safari 3.2.2, says it's not supported on
Windows

[1] http://prototypejs.org/download

FWIW,

-- T.J. :-)

On Mar 20, 8:59 pm, kangax kan...@gmail.com wrote:
 On Mar 20, 3:03 pm, T.J. Crowder t...@crowdersoftware.com wrote:

  Thanks, Tobie.  That was the missing bit all right.  The contribute
  page _does_ mention rake test, but much further down; I'll update
  the page to tie things together a bit.

  Out of curiousity, anyone successfully run the tests lately on Chrome,
  IE7, or Opera on Windows?  

 I'm on mac. Trunk fully passes FF3 and Safari 4 here. There are a
 couple of failures in Opera 9.64. I'm taking care of IE8 at the moment
 - just pushed few fixes for DOM suite.

 [...]

 --
 kangax
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Cloned repo via git, not seeing the unit test html files

2009-03-20 Thread Tobie Langel

Sure.

And that would warrant some documentation too.

The tests are generated from the js test files.

You'll need to run rake test for that.

Which in turn will prompt you to require unittest_js submodules.

Let me know how things go.

Best,

Tobie

On Mar 20, 10:39 am, T.J. Crowder t...@crowdersoftware.com wrote:
 Hi all,

 I don't seem to be seeing the unit test HTML files.  Apologies if I've
 done something daft, but I'm running out the door so I thought I'd
 ping in hopes of being able to work on stuff (I have a bunch of doc
 tickets to deal with) later this afternoon.

 I've installed Ruby, Git, etc. and have cloned the repo and
 successfully built via rake dist.  According to the contribute page:

  To see what unit tests look like, open up any of the HTML documents
 found in test/unit/ in your browser.  They run automatically, so you
 should see a flurry of green-colored rows after a few moments.

 There aren't any HTML files in test/unit at all (there are several
 JavaScript files that look like they may well implement certain
 specific tests).  There are some HTML files elsewhere in the tree, but
 so far nothing I've found looks like the bunch of green rows
 described.  Could someone point me at it or give me an idea where I
 may have gone astray?

 Thanks in advance,
 --
 T.J. Crowder
 tj / crowder software / com
 Independent Software Engineer, consulting services available
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Cloned repo via git, not seeing the unit test html files

2009-03-20 Thread T.J. Crowder

Thanks, Tobie.  That was the missing bit all right.  The contribute
page _does_ mention rake test, but much further down; I'll update
the page to tie things together a bit.

Out of curiousity, anyone successfully run the tests lately on Chrome,
IE7, or Opera on Windows?  For me, Firefox 3 runs and passes all
tests, but Chrome (1.0.154.48) doesn't even launch and I have to kill
rake; IE7 fails several tests; and Opera (9.64) runs many of the tests
(and as per the warning I have to manually close it per test), but
then dies in the middle -- Opera not running but rake seeming to be
waiting for it.  This is with rake version 0.7.3 (I just today
installed Ruby and rake via the One Click Ruby Installer linked from
the contribute page) and a fresh clone of the repo.

I haven't had time to look into these in any detail at all, but
thought I'd ask the question, in case someone already knows what's
going on there.

Thanks,

-- T.J. :-)

On Mar 20, 1:44 pm, Tobie Langel tobie.lan...@gmail.com wrote:
 Sure.

 And that would warrant some documentation too.

 The tests are generated from the js test files.

 You'll need to run rake test for that.

 Which in turn will prompt you to require unittest_js submodules.

 Let me know how things go.

 Best,

 Tobie

 On Mar 20, 10:39 am, T.J. Crowder t...@crowdersoftware.com wrote:

  Hi all,

  I don't seem to be seeing the unit test HTML files.  Apologies if I've
  done something daft, but I'm running out the door so I thought I'd
  ping in hopes of being able to work on stuff (I have a bunch of doc
  tickets to deal with) later this afternoon.

  I've installed Ruby, Git, etc. and have cloned the repo and
  successfully built via rake dist.  According to the contribute page:

   To see what unit tests look like, open up any of the HTML documents
  found in test/unit/ in your browser.  They run automatically, so you
  should see a flurry of green-colored rows after a few moments.

  There aren't any HTML files in test/unit at all (there are several
  JavaScript files that look like they may well implement certain
  specific tests).  There are some HTML files elsewhere in the tree, but
  so far nothing I've found looks like the bunch of green rows
  described.  Could someone point me at it or give me an idea where I
  may have gone astray?

  Thanks in advance,
  --
  T.J. Crowder
  tj / crowder software / com
  Independent Software Engineer, consulting services available


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---



[Prototype-core] Re: Cloned repo via git, not seeing the unit test html files

2009-03-20 Thread kangax

On Mar 20, 3:03 pm, T.J. Crowder t...@crowdersoftware.com wrote:
 Thanks, Tobie.  That was the missing bit all right.  The contribute
 page _does_ mention rake test, but much further down; I'll update
 the page to tie things together a bit.

 Out of curiousity, anyone successfully run the tests lately on Chrome,
 IE7, or Opera on Windows?  

I'm on mac. Trunk fully passes FF3 and Safari 4 here. There are a
couple of failures in Opera 9.64. I'm taking care of IE8 at the moment
- just pushed few fixes for DOM suite.

[...]

--
kangax
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Prototype: Core group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to 
prototype-core-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/prototype-core?hl=en
-~--~~~~--~~--~--~---