similar to: Concerns over Rails' handling of tests

Hello, I am looking for a user test automation tool. When I say ''user'', I mean it should mimic the user interacting with the app. That ultimately boils down to a tool that drives a browser or is able to make http requests and allow us to deal easily with the responses. Our requirements are to be able to write the tests in Ruby (no need to switch to other language for test

Yes, I believe it is and I think it is dangerous, and confusing to people new to the concepts of testing. I''ve mentioned a point similar to this on here before, but with the announcement of Rails "integration" test, I''m worried that somebody somewhere is getting their types of tests worryingly mixed up. Lets start with what we had in the beginning...unit tests (for

The "rspec" rake task collects all _spec files in the spec directory, and excludes the "watir" directory. Is this indicating a preference for using Watir over Selenium? I would like it better to standardize on something more neutral, ''ui'' perhaps? /Marcus -- Marcus Ahnve http://marcus.ahnve.net

This is related to Selenium/Watir usage along side webrat in story testing. MHS_Testing and Rspec-ui provide some great help for testing through frameworks like Selenium/Watir. But there is something missing, Webrat has changed the landscape somewhat with Acceptance Tests/Story Driven development. Now I have a choice: 1. Tests and rails process run as one test process (Webrat) 2. Use

Hey all, I am currently working on coming up w/ an easy to use, developer-centric web testing framework to test a J2EE app with. (I have 3 rails apps in production, love rspec, and am currently at a java shop). I''ve looked at selenium, and it just doesn''t seem like it is ready for prime time, and the target audience is developers. So, having said that, does the rspec

RSpec 0.9.4 has just been released. Gems haven''t rsync''ed around the globe yet, so you might have to wait a few hours to install it. The big news this time is Spec::Ui 0.2.0, which has been released along with RSpec core. This RSpec extension gives you custom Watir matchers (custom Selenium-RC matchers are not implemented yet). Moreover, it comes with a custom KICK ASS formatter

While looking into spec_ui, I decided to run the examples. The watir example works a little, but always chokes on the ''better than fudge'' spec (failure output below). Also, is there any command to pause the "browser"? If my connection slows, the test gets out of whack. The selenium example fails right away (output below). I do have the 0.9.0 selenium-rc

Hello, I wonder if some of you have evaluated these two solutions and how they compares each other. What did you liked or disliked ? And may be are you aware of others functionnal testing tools usable with and integrated with Ruby ? Thanks -- Posted via http://www.ruby-forum.com/.

RSpeckers: I went with RSpec instead of Systir because I downloaded and installed the former first. (I know that''s not exactly a ringing endorsement! ;-) I want to compete with FIT and Fitnesse, like this: http://www.zeroplayer.com/cgi-bin/wiki?TestFlea#tropism (Click on a Green Bar to distend one test case.) I want a domain-specific language in the parchment-colored area on the

Being new to testing and ruby, are there "standard" tests that can be done that test for things like cross site scripting and friends? If not, anyone have ideas on what I might do about testing those sorts of things? I''ll be using rails, also. Mike B. ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging

I really have no more input than that, so the subject speaks for itself. How do you test that AJAX effects shown in the browser are actually happening? Maybe an auto-complete form field is a good starting example. Sean

Hi, Is there a hook or a method to execute some code after a whole feature has run or will I need to embed that in a ''Then''? Regards Aidy

I have been using Rspec stories with Webrat feeling very productive and happy. Then I needed to do something with Selenium (Webrat could have done what I needed but it does not yet have the functionality). Selenium-core as part of a rails plugin looked nice but did not seem to fit with rspec stories. So I went the Selenium-rc route. Since Selenium uses a separate instance of rails

One of the things I like about Rails is the built-in support for testing ? it?s almost hard not to write tests. But even if I write extensive tests (currently ?Code to Test Ratio: 1:3.4? according to rake stats in a small toy project) I still feel that it?s not enough. I occasionally get the urge to fire up the browser and click around to test that everything works. You shouldn?t have to

As I work with Rails TestUnit tests I am reconsidering how to use cucumber features. It seems to me that it might be best to have a coherent view of how to arrange my test suites before I get much further into this. Now, so far I have considered three possibilities: 1. Use features exclusively. Create a feature file for each model, one for each controller and possibly an additional one for

Hi! I''m using cucumber + selenium and I love it. However I''m looking to add some methods (example: click_and_wait etc) to the lib. Therefore looked around a bit and I got two questions: Firstly about rspec-ui, I''m a little confused, does rspec-ui overlap with its propose with webrat with cucumber or I''m missing a point? Secondly, are there any plans to

I''m evaluating what to use for integration testing: SafariWatir - integrates nicely with RSpec - doesn''t work with Ajax because of Safari event firing issues Selenium - Works with Ajax - doesn''t integrate with RSpec What is the best guess timeframe for RSpec integration testing? Will it be able to test Ajax application in the early iterations? Thanks, Brian Yamabe

Hi all. If I run rake features or cucumber features/* I get one failing FIT scenario in one of my features. If I then run that feature that contains the FIT table with the failing scenario manually, it passes. I run it again with rake features or cucumber features/* it fails, run individually, it passes. Obviously some state is carrying over between the features. Any idea where i would start

I don''t even know how it''d be possible (through Selenium?), but I want it. I want to see if my stupid CSS hacks break. I want to say: describe "#nav-column" do body = something("#body-column") it "should line up at the top" do dom[:top].should_be == body.dom[:top] end it "should always be to the right" do

I like Shoulda. Sometimes I like plain old Test::Unit. Cucumber gives me a different thought process. I''d just like to hear some thoughts on why RSpec? What does it buy me that I can''t get with Shoulda? I just can''t seem to think in RSpec. Where is there a good example of RSpec tests that will help me grasp the right path? Thanks! -- Amos King