5

I used to be able to launch all my Selenium2 WebDriver tests in Ruby on Rails via rake test:units.

But recently, my test case(s) won't be found anymore. I don't get any notification or error message. Traced, the test just ends after Execute test:units

It still can be launched manually by calling rake test:unit TEST=test/unit/foo_bar or using ruby [path] to launch the file.

The test itself still works just fine, so I don't know why the automatic test doesn't start anymore. Maybe I violated some naming conventions? This is how everything is named:

  • File: foo_bar.rb
  • Class: FooBar
  • Method: test_foo_bar

Further I use some additional self-written requirements stored in test/unit/helpers.

Might this be another source of problems?

Improve this question
2
  • 1
    I've read properly or you really said unit test implemented with webdriver?
    – lorenzo.urbini
    Commented May 28, 2012 at 7:48
  • Which browser are you testing with, I had some problems when a remote FireFox node upgraded itself so each time Selenium started it had a dialog asking a "user" to check plugins updates. This blocked selenium running properly and caused all our tests to timeout.
    – Toby Jackson
    Commented Mar 29, 2013 at 19:14

1 Answer 1

Reset to default
1

If you use unit testing framework Test:units then yes it have naming conventions. You can read more from Test::Unit.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.