Re: [Wtr-general] FireWatir on Intel Mac
On 6/27/06, Chris McMahon <[EMAIL PROTECTED]> wrote: If I'm not mistaken, it's because the build depends on C:\ruby\lib\ruby\gems\1.8\gems\watir-1.5.0.945\watir\win32ole\win32ole.so and this was not interpreted correctly on the Mac? That is, there is no context for win32ole on platforms other than Windows? More or less. I got firewatir working on my Mac Book Pro a little while ago, and found the performance too lacking to do much more with it. Attached is a patch to firewatir's watir.rb that allowed me to get it working (for educational purposes only). I had to comment out things like winClicker etc. I suppose these could be conditionally included. What's the latest on firewatir? Are there plans to merge it back into the main watir codebase? Is jssh the long-term plan for integrating watir into firefox? This is definitely something I'd like to jump in and help hack on. From my perspective I'd like to make some fairly sweeping changes to the code, particularly the global variable for the jssh socket and hard-coded javascript in each method, but I don't want to interfere with anyone else if they're currently working on it. If someone could inform me of the plans for the firewatir code, that would be great. Cheers, /Nick firewatir-mac.patch Description: Binary data ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] AWESOME Ruby Hacks
On 7/26/06, Jesper Rønn-Jensen <[EMAIL PROTECTED]> wrote: On 7/26/06, Michael Bolton < [EMAIL PROTECTED]> wrote: http://blog.nicksieger.com/articles/2006/04/23/tweaking-irb This outlines some wonderful things about how to hack your IRB configurationfile to do some totally awesome things, including What a great trick. Thanks a lot for sharing.Glad that you guys are finding it useful! Unfortunately, Nicks blog post was not open for comments (or something else went wrong so I couldn't comment).Sorry about that, I had comments closing after 10 days -- see no real reason to do that. Would you mind trying again? Cheers,/Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] OT: anyone tried JRuby?
On 1/19/07, Chris McMahon <[EMAIL PROTECTED]> wrote: Martin Fowler says "it works a treat" http://martinfowler.com/bliki/JRubyVelocity.html I just wondered if anyone here has spiked anything with JRuby. I use it quite a bit, but then again I'm one of the developers :) Of course, it's unfortunately not going to fit the bill yet for WATiR since it relies on Win32::OLE which is implemented in C on matzruby, and we don't have a replacement for JRuby yet. Other than that, feel free to try it out and send reports over to the JRuby mailing list! http://xircles.codehaus.org/projects/jruby/lists Cheers, /Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] OT: anyone tried JRuby?
On 1/19/07, Bret Pettichord <[EMAIL PROTECTED]> wrote: Nick, Thanks for the update. Could i use DRB to connect JRuby to a MatzRuby process running Watir? I haven't used DRb on JRuby yet personally, but I've heard reports of some people using it successfully. That said, I'll caveat by saying that we have another limitation of not having a full-fledged implementation of the Ruby Marshal module. This is a high priority for us to fix though, because Rails session persistence depends on it. A quick search of our JIRA shows some issues open, some closed. http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&&pid=11295&query=drb&summary=true&description=true&body=true /Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] OT: Test unit reporter project dead?
On 2/16/07, Charley Baker <[EMAIL PROTECTED]> wrote: I've been using test unit reporter for some time. I just tried to look up the page on Rubyforge for a friend and now I'm getting an Invalid Project page at http://rubyforge.org/project/test-report/ and the project site listed in the readme for test-report. Sending a message to Alexey about it, just curious if anyone knows anything about this? Might be a temporary fluke on Rubyforge. Slightly shameless plug -- you might be interested in my CI::Reporter [1] package that I released recently. Cheers, /Nick [1] http://caldersphere.rubyforge.org/ci_reporter ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] OT: Test unit reporter project dead?
On 2/17/07, Charley Baker <[EMAIL PROTECTED]> wrote: I guess I'm not too surprised, its been a long time since there's been any active development on the project, it is definitely a big void to fill however. Nick, glad to hear about ci reporter, I will definitely be taking a look at it. I'm currently using the xml output of test runs through test reporter for Cruise Control, the only modification I've made is to add assertion counts to the report. I'm not tracking assertion counts right now in CI::Reporter, so if you end up making the same change again, feel free to send me a patch and I'd be happy to add it. /Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] OT: Test unit reporter project dead?
On 2/23/07, Brian Reynolds <[EMAIL PROTECTED]> wrote: Continuous Integration Enthusiast but Ruby Newbie here... First off, Nick, thanks for putting something together for test reporting. Now down to business, I want to make my watir tests display in CruiseControl. I can run a ruby test easy enough from ant, but don't know how to get the ci_reporter class to print out my results so that it gets displayed in the build report. Can someone show me how to alter this Watir sample test to use ci_reporter? *** require 'watir' include Watir require 'test/unit' require 'rubygems' require 'ci/reporter/rake/test_unit_loader' should work, if you have the gem installed. (I guess the "rake" in the path doesn't make much sense here :) You should only have to require it once for your whole test suite (e.g., to avoid cluttering requires for each test case class), so you could put it in a test_helper.rb file if you have one. The other bit is that it will write its report files to "test/reports", unless you set the ENV variable "CI_REPORTS" to a directory where they should be written. This directory should be in synch with CruiseControl. Also, have a look at http://caldersphere.rubyforge.org/ci_reporter/ and let me know if any of the docs are unclear (plus I may not have captured all these details there in my haste to get a release out). Since this is a little off-topic for this list, feel free to mail off list if you have more questions. Cheers, /Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] OT: Test unit reporter project dead?
On 2/23/07, Nick Sieger <[EMAIL PROTECTED]> wrote: Can someone show me how to alter this Watir sample test to use > ci_reporter? > > *** > require 'watir' > include Watir > require 'test/unit' require 'rubygems' gem 'ci_reporter' require 'ci/reporter/rake/test_unit_loader' Forgot the "gem" line above; it's important as ci_reporter is not auto-required by rubygems. /Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] OT: Test unit reporter project dead?
On 2/26/07, Bret Pettichord <[EMAIL PROTECTED]> wrote: > Nick Sieger wrote: > > The other bit is that it will write its report files to > > "test/reports", unless you set the ENV variable "CI_REPORTS" to a > > directory where they should be written. > I didn't know to look here. I installed ci_reporter today and had to > read the source to figure this out (I should have read my email first...) > > It would be good to spell this out in the docs. Thanks very much Nick > for this tool. Yeah, sorry about that. I rushed writing the docs a little bit because I wanted to get the first release out the door and forgot to mention this. The docs contains this information now. Thanks, /Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] ci-reporter question
On 2/27/07, Ethan Jewett <[EMAIL PROTECTED]> wrote: > "gem" replaced "require_gem", sort of - > http://redhanded.hobix.com/bits/require_gemIsDeprecated.html > > However, you seem to have a recent enough version of rubygems that > this shouldn't be a problem. Maybe there's a missing require > 'rubygems' somewhere? > That's what I would suspect too. Maybe I missed it somewhere in the load sequence for test unit. /Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Will 'ci_reporter' work within 'test unit' 'test suite' execution?
On 3/30/07, Brad <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to figure out how to use 'ci_reporter' within 'test unit' and > 'test suite'. Below is the code that I had working when 'test reporter' was > active. Unsure on the line labeled 'what goes here'. > > FileUtils.mkdir_p 'build/report' > FileUtils.mkdir_p 'logs' > $args = 'report' > if $args == "report" > **what goes here** > #Test::Unit::UI::Reporter.run(TestSuite_AllTests,'build/report',:html) > elsif > Test::Unit::UI::Console::TestRunner.run(TestSuite_AllTests) > end CI::Reporter auto-injects itself when you require 'ci/reporter/rake/test_unit_loader'. Try eliminating the entire if ... else ... end block and just leaving the TestRunner.run line: Test::Unit::UI::Console::TestRunner.run(TestSuite_AllTests) /Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Porting Watir to JRuby
On 6/13/07, Nivetha Padmanaban <[EMAIL PROTECTED]> wrote: > > Any plans of porting WATIR to JRuby?? None that I know of at the moment. The stumbling block is to get a compatible version of 'win32ole' on JRuby which we don't have. /Nick ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
