capybara 1.1.4 → 2.0.0.beta2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (84) hide show
  1. data/History.txt +100 -0
  2. data/License.txt +22 -0
  3. data/README.md +829 -0
  4. data/lib/capybara.rb +124 -6
  5. data/lib/capybara/cucumber.rb +2 -5
  6. data/lib/capybara/driver/base.rb +5 -5
  7. data/lib/capybara/driver/node.rb +2 -2
  8. data/lib/capybara/dsl.rb +3 -121
  9. data/lib/capybara/node/actions.rb +12 -28
  10. data/lib/capybara/node/base.rb +5 -13
  11. data/lib/capybara/node/element.rb +21 -21
  12. data/lib/capybara/node/finders.rb +27 -89
  13. data/lib/capybara/node/matchers.rb +107 -69
  14. data/lib/capybara/node/simple.rb +11 -13
  15. data/lib/capybara/query.rb +78 -0
  16. data/lib/capybara/rack_test/browser.rb +16 -27
  17. data/lib/capybara/rack_test/driver.rb +11 -1
  18. data/lib/capybara/rack_test/node.rb +17 -1
  19. data/lib/capybara/result.rb +84 -0
  20. data/lib/capybara/rspec/matchers.rb +28 -63
  21. data/lib/capybara/selector.rb +97 -33
  22. data/lib/capybara/selenium/driver.rb +14 -61
  23. data/lib/capybara/selenium/node.rb +6 -15
  24. data/lib/capybara/server.rb +32 -27
  25. data/lib/capybara/session.rb +54 -30
  26. data/lib/capybara/spec/public/jquery-ui.js +791 -0
  27. data/lib/capybara/spec/public/jquery.js +9046 -0
  28. data/lib/capybara/spec/public/test.js +4 -1
  29. data/lib/capybara/spec/session.rb +56 -27
  30. data/lib/capybara/spec/session/all_spec.rb +8 -4
  31. data/lib/capybara/spec/session/attach_file_spec.rb +12 -9
  32. data/lib/capybara/spec/session/check_spec.rb +6 -3
  33. data/lib/capybara/spec/session/choose_spec.rb +4 -1
  34. data/lib/capybara/spec/session/click_button_spec.rb +5 -14
  35. data/lib/capybara/spec/session/click_link_or_button_spec.rb +2 -1
  36. data/lib/capybara/spec/session/click_link_spec.rb +3 -17
  37. data/lib/capybara/spec/session/current_url_spec.rb +77 -9
  38. data/lib/capybara/spec/session/fill_in_spec.rb +8 -18
  39. data/lib/capybara/spec/session/find_spec.rb +19 -46
  40. data/lib/capybara/spec/session/first_spec.rb +2 -34
  41. data/lib/capybara/spec/session/has_css_spec.rb +1 -1
  42. data/lib/capybara/spec/session/has_field_spec.rb +28 -0
  43. data/lib/capybara/spec/session/has_select_spec.rb +84 -31
  44. data/lib/capybara/spec/session/has_table_spec.rb +7 -69
  45. data/lib/capybara/spec/session/has_text_spec.rb +168 -0
  46. data/lib/capybara/spec/session/javascript.rb +65 -81
  47. data/lib/capybara/spec/session/node_spec.rb +115 -0
  48. data/lib/capybara/spec/session/screenshot.rb +29 -0
  49. data/lib/capybara/spec/session/select_spec.rb +12 -12
  50. data/lib/capybara/spec/session/text_spec.rb +9 -4
  51. data/lib/capybara/spec/session/unselect_spec.rb +12 -6
  52. data/lib/capybara/spec/session/visit_spec.rb +76 -0
  53. data/lib/capybara/spec/session/within_frame_spec.rb +33 -0
  54. data/lib/capybara/spec/session/within_spec.rb +47 -58
  55. data/lib/capybara/spec/session/within_window_spec.rb +40 -0
  56. data/lib/capybara/spec/test_app.rb +27 -3
  57. data/lib/capybara/spec/views/form.erb +11 -10
  58. data/lib/capybara/spec/views/host_links.erb +2 -2
  59. data/lib/capybara/spec/views/tables.erb +6 -66
  60. data/lib/capybara/spec/views/with_html.erb +3 -3
  61. data/lib/capybara/spec/views/with_js.erb +11 -8
  62. data/lib/capybara/util/save_and_open_page.rb +4 -3
  63. data/lib/capybara/version.rb +1 -1
  64. data/spec/basic_node_spec.rb +15 -3
  65. data/spec/dsl_spec.rb +12 -10
  66. data/spec/rack_test_spec.rb +152 -0
  67. data/spec/rspec/features_spec.rb +0 -2
  68. data/spec/rspec/matchers_spec.rb +164 -89
  69. data/spec/rspec_spec.rb +0 -2
  70. data/spec/selenium_spec.rb +67 -0
  71. data/spec/server_spec.rb +35 -23
  72. data/spec/spec_helper.rb +18 -2
  73. metadata +30 -30
  74. data/README.rdoc +0 -722
  75. data/lib/capybara/spec/driver.rb +0 -301
  76. data/lib/capybara/spec/session/current_host_spec.rb +0 -68
  77. data/lib/capybara/spec/session/has_content_spec.rb +0 -106
  78. data/lib/capybara/util/timeout.rb +0 -27
  79. data/spec/driver/rack_test_driver_spec.rb +0 -89
  80. data/spec/driver/selenium_driver_spec.rb +0 -37
  81. data/spec/session/rack_test_session_spec.rb +0 -55
  82. data/spec/session/selenium_session_spec.rb +0 -26
  83. data/spec/string_spec.rb +0 -77
  84. data/spec/timeout_spec.rb +0 -28
@@ -1,7 +1,5 @@
1
1
  require 'spec_helper'
2
2
 
3
- Capybara.app = TestApp
4
-
5
3
  describe 'capybara/rspec', :type => :request do
6
4
  it "should include Capybara in rspec" do
7
5
  visit('/foo')
@@ -0,0 +1,67 @@
1
+ require 'spec_helper'
2
+
3
+ describe Capybara::Session do
4
+ context 'with selenium driver' do
5
+ before do
6
+ @session = TestSessions::Selenium
7
+ end
8
+
9
+ describe '#driver' do
10
+ it "should be a selenium driver" do
11
+ @session.driver.should be_an_instance_of(Capybara::Selenium::Driver)
12
+ end
13
+ end
14
+
15
+ describe '#mode' do
16
+ it "should remember the mode" do
17
+ @session.mode.should == :selenium
18
+ end
19
+ end
20
+
21
+ it_should_behave_like "session"
22
+ it_should_behave_like "session with javascript support"
23
+ it_should_behave_like "session with screenshot support"
24
+ it_should_behave_like "session with frame support"
25
+ it_should_behave_like "session with window support"
26
+ it_should_behave_like "session without headers support"
27
+ it_should_behave_like "session without status code support"
28
+
29
+ unless RbConfig::CONFIG['host_os'] =~ /mswin|mingw/
30
+ it "should not interfere with forking child processes" do
31
+ # Launch a browser, which registers the at_exit hook
32
+ browser = Capybara::Selenium::Driver.new(TestApp).browser
33
+
34
+ # Fork an unrelated child process. This should not run the code in the at_exit hook.
35
+ begin
36
+ pid = fork { "child" }
37
+ Process.wait2(pid)[1].exitstatus.should == 0
38
+ rescue NotImplementedError
39
+ # Fork unsupported (e.g. on JRuby)
40
+ end
41
+
42
+ browser.quit
43
+ end
44
+ end
45
+
46
+ describe "exit codes" do
47
+ before do
48
+ @current_dir = Dir.getwd
49
+ Dir.chdir(File.join(File.dirname(__FILE__), '..'))
50
+ end
51
+
52
+ after do
53
+ Dir.chdir(@current_dir)
54
+ end
55
+
56
+ it "should have return code 1 when running selenium_driver_rspec_failure.rb" do
57
+ `rspec spec/fixtures/selenium_driver_rspec_failure.rb`
58
+ $?.exitstatus.should be 1
59
+ end
60
+
61
+ it "should have return code 0 when running selenium_driver_rspec_success.rb" do
62
+ `rspec spec/fixtures/selenium_driver_rspec_success.rb`
63
+ $?.exitstatus.should be 0
64
+ end
65
+ end
66
+ end
67
+ end
@@ -17,6 +17,16 @@ describe Capybara::Server do
17
17
  end.should_not raise_error
18
18
  end
19
19
 
20
+ it "should bind to the specified host" do
21
+ Capybara.server_host = '0.0.0.0'
22
+
23
+ app = proc { |env| [200, {}, "Hello Server!"]}
24
+ server = Capybara::Server.new(app).boot
25
+ server.host.should == '0.0.0.0'
26
+
27
+ Capybara.server_host = nil
28
+ end
29
+
20
30
  it "should use specified port" do
21
31
  Capybara.server_port = 22789
22
32
 
@@ -29,6 +39,16 @@ describe Capybara::Server do
29
39
  Capybara.server_port = nil
30
40
  end
31
41
 
42
+ it "should use given port" do
43
+ @app = proc { |env| [200, {}, "Hello Server!"]}
44
+ @server = Capybara::Server.new(@app, 22790).boot
45
+
46
+ @res = Net::HTTP.start(@server.host, 22790) { |http| http.get('/') }
47
+ @res.body.should include('Hello Server')
48
+
49
+ Capybara.server_port = nil
50
+ end
51
+
32
52
  it "should find an available port" do
33
53
  @app1 = proc { |env| [200, {}, "Hello Server!"]}
34
54
  @app2 = proc { |env| [200, {}, "Hello Second Server!"]}
@@ -62,28 +82,20 @@ describe Capybara::Server do
62
82
  @server2a.port.should == @server2b.port
63
83
  end
64
84
 
65
- it "should wait specified time for the app to boot" do
66
- pending 'this test does not work: https://groups.google.com/d/msg/ruby-capybara/QrSKTbjh5rY/egvcVFYiWZMJ'
67
-
68
- @slow_app = proc { |env| sleep(1); [200, {}, "Hello Slow Server!"] }
69
-
70
- Capybara.server_boot_timeout = 1.5
71
- @server = Capybara::Server.new(@slow_app).boot
72
-
73
- @res = Net::HTTP.start(@server.host, @server.port) { |http| http.get('/') }
74
- @res.body.should include('Hello Slow Server')
75
- end
76
-
77
- it "should raise an exception if boot timeout is exceeded" do
78
- pending 'this test does not work: https://groups.google.com/d/msg/ruby-capybara/QrSKTbjh5rY/egvcVFYiWZMJ'
79
-
80
- @slow_app = proc { |env| sleep(1); [200, {}, "Hello Slow Server!"] }
81
-
82
- Capybara.server_boot_timeout = 0.5
83
- server = Capybara::Server.new(@slow_app)
84
- server.stub(:exit).and_return(:timeout)
85
- server.stub(:puts)
86
- server.boot.should == :timeout
85
+ it "should raise server errors when the server errors before the timeout" do
86
+ begin
87
+ Capybara.server do
88
+ sleep 0.1
89
+ raise 'kaboom'
90
+ end
91
+
92
+ proc do
93
+ Capybara::Server.new(proc {|e|}).boot
94
+ end.should raise_error(RuntimeError, 'kaboom')
95
+ ensure
96
+ # TODO refactor out the defaults so it's reliant on unset state instead of
97
+ # a one-time call in capybara.rb
98
+ Capybara.server {|app, port| Capybara.run_default_server(app, port)}
99
+ end
87
100
  end
88
-
89
101
  end
@@ -12,19 +12,35 @@ RSpec.configure do |config|
12
12
  config.default_selector = :xpath
13
13
  end
14
14
  end
15
+
16
+ # Workaround for http://code.google.com/p/selenium/issues/detail?id=3147:
17
+ # Rerun the example if we hit a transient "docElement is null" error
18
+ config.around(:each) do |example|
19
+ attempts = 0
20
+ begin
21
+ example.run
22
+ # example is just a Proc, @example is the current RSpec::Core::Example
23
+ e = @example.instance_variable_get('@exception') # usually nil
24
+ if (defined?(Selenium::WebDriver::Error::UnknownError) && e.is_a?(Selenium::WebDriver::Error::UnknownError) &&
25
+ e.message == 'docElement is null' && (attempts += 1) < 5)
26
+ @example.instance_variable_set('@exception', nil)
27
+ redo
28
+ end
29
+ end until true
30
+ end
15
31
  end
16
32
 
17
33
  # Required here instead of in rspec_spec to avoid RSpec deprecation warning
18
34
  require 'capybara/rspec'
19
35
 
20
- require 'capybara/spec/driver'
21
36
  require 'capybara/spec/session'
22
37
 
23
38
  alias :running :lambda
24
39
 
40
+ Capybara.app = TestApp
25
41
  Capybara.default_wait_time = 0 # less timeout so tests run faster
26
42
 
27
43
  module TestSessions
28
44
  RackTest = Capybara::Session.new(:rack_test, TestApp)
29
45
  Selenium = Capybara::Session.new(:selenium, TestApp)
30
- end
46
+ end
metadata CHANGED
@@ -1,15 +1,15 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: capybara
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.1.4
5
- prerelease:
4
+ version: 2.0.0.beta2
5
+ prerelease: 6
6
6
  platform: ruby
7
7
  authors:
8
8
  - Jonas Nicklas
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2012-11-28 00:00:00.000000000 Z
12
+ date: 2012-07-13 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: nokogiri
@@ -98,7 +98,7 @@ dependencies:
98
98
  requirements:
99
99
  - - ~>
100
100
  - !ruby/object:Gem::Version
101
- version: 0.1.4
101
+ version: 1.0.0.beta1
102
102
  type: :runtime
103
103
  prerelease: false
104
104
  version_requirements: !ruby/object:Gem::Requirement
@@ -106,7 +106,7 @@ dependencies:
106
106
  requirements:
107
107
  - - ~>
108
108
  - !ruby/object:Gem::Version
109
- version: 0.1.4
109
+ version: 1.0.0.beta1
110
110
  - !ruby/object:Gem::Dependency
111
111
  name: sinatra
112
112
  requirement: !ruby/object:Gem::Requirement
@@ -130,7 +130,7 @@ dependencies:
130
130
  requirements:
131
131
  - - ! '>='
132
132
  - !ruby/object:Gem::Version
133
- version: 2.0.0
133
+ version: 2.2.0
134
134
  type: :development
135
135
  prerelease: false
136
136
  version_requirements: !ruby/object:Gem::Requirement
@@ -138,13 +138,13 @@ dependencies:
138
138
  requirements:
139
139
  - - ! '>='
140
140
  - !ruby/object:Gem::Version
141
- version: 2.0.0
141
+ version: 2.2.0
142
142
  - !ruby/object:Gem::Dependency
143
143
  name: launchy
144
144
  requirement: !ruby/object:Gem::Requirement
145
145
  none: false
146
146
  requirements:
147
- - - ~>
147
+ - - ! '>='
148
148
  - !ruby/object:Gem::Version
149
149
  version: 2.0.4
150
150
  type: :development
@@ -152,7 +152,7 @@ dependencies:
152
152
  version_requirements: !ruby/object:Gem::Requirement
153
153
  none: false
154
154
  requirements:
155
- - - ~>
155
+ - - ! '>='
156
156
  - !ruby/object:Gem::Version
157
157
  version: 2.0.4
158
158
  - !ruby/object:Gem::Dependency
@@ -194,7 +194,7 @@ dependencies:
194
194
  requirements:
195
195
  - - ! '>='
196
196
  - !ruby/object:Gem::Version
197
- version: '0.10'
197
+ version: 0.10.5
198
198
  type: :development
199
199
  prerelease: false
200
200
  version_requirements: !ruby/object:Gem::Requirement
@@ -202,7 +202,7 @@ dependencies:
202
202
  requirements:
203
203
  - - ! '>='
204
204
  - !ruby/object:Gem::Version
205
- version: '0.10'
205
+ version: 0.10.5
206
206
  - !ruby/object:Gem::Dependency
207
207
  name: rake
208
208
  requirement: !ruby/object:Gem::Requirement
@@ -225,8 +225,7 @@ email:
225
225
  - jonas.nicklas@gmail.com
226
226
  executables: []
227
227
  extensions: []
228
- extra_rdoc_files:
229
- - README.rdoc
228
+ extra_rdoc_files: []
230
229
  files:
231
230
  - lib/capybara/cucumber.rb
232
231
  - lib/capybara/driver/base.rb
@@ -239,11 +238,13 @@ files:
239
238
  - lib/capybara/node/finders.rb
240
239
  - lib/capybara/node/matchers.rb
241
240
  - lib/capybara/node/simple.rb
241
+ - lib/capybara/query.rb
242
242
  - lib/capybara/rack_test/browser.rb
243
243
  - lib/capybara/rack_test/driver.rb
244
244
  - lib/capybara/rack_test/form.rb
245
245
  - lib/capybara/rack_test/node.rb
246
246
  - lib/capybara/rails.rb
247
+ - lib/capybara/result.rb
247
248
  - lib/capybara/rspec/features.rb
248
249
  - lib/capybara/rspec/matchers.rb
249
250
  - lib/capybara/rspec.rb
@@ -252,9 +253,10 @@ files:
252
253
  - lib/capybara/selenium/node.rb
253
254
  - lib/capybara/server.rb
254
255
  - lib/capybara/session.rb
255
- - lib/capybara/spec/driver.rb
256
256
  - lib/capybara/spec/fixtures/capybara.jpg
257
257
  - lib/capybara/spec/fixtures/test_file.txt
258
+ - lib/capybara/spec/public/jquery-ui.js
259
+ - lib/capybara/spec/public/jquery.js
258
260
  - lib/capybara/spec/public/test.js
259
261
  - lib/capybara/spec/session/all_spec.rb
260
262
  - lib/capybara/spec/session/attach_file_spec.rb
@@ -263,7 +265,6 @@ files:
263
265
  - lib/capybara/spec/session/click_button_spec.rb
264
266
  - lib/capybara/spec/session/click_link_or_button_spec.rb
265
267
  - lib/capybara/spec/session/click_link_spec.rb
266
- - lib/capybara/spec/session/current_host_spec.rb
267
268
  - lib/capybara/spec/session/current_url_spec.rb
268
269
  - lib/capybara/spec/session/fill_in_spec.rb
269
270
  - lib/capybara/spec/session/find_button_spec.rb
@@ -273,22 +274,27 @@ files:
273
274
  - lib/capybara/spec/session/find_spec.rb
274
275
  - lib/capybara/spec/session/first_spec.rb
275
276
  - lib/capybara/spec/session/has_button_spec.rb
276
- - lib/capybara/spec/session/has_content_spec.rb
277
277
  - lib/capybara/spec/session/has_css_spec.rb
278
278
  - lib/capybara/spec/session/has_field_spec.rb
279
279
  - lib/capybara/spec/session/has_link_spec.rb
280
280
  - lib/capybara/spec/session/has_select_spec.rb
281
281
  - lib/capybara/spec/session/has_selector_spec.rb
282
282
  - lib/capybara/spec/session/has_table_spec.rb
283
+ - lib/capybara/spec/session/has_text_spec.rb
283
284
  - lib/capybara/spec/session/has_xpath_spec.rb
284
285
  - lib/capybara/spec/session/headers.rb
285
286
  - lib/capybara/spec/session/javascript.rb
287
+ - lib/capybara/spec/session/node_spec.rb
286
288
  - lib/capybara/spec/session/response_code.rb
289
+ - lib/capybara/spec/session/screenshot.rb
287
290
  - lib/capybara/spec/session/select_spec.rb
288
291
  - lib/capybara/spec/session/text_spec.rb
289
292
  - lib/capybara/spec/session/uncheck_spec.rb
290
293
  - lib/capybara/spec/session/unselect_spec.rb
294
+ - lib/capybara/spec/session/visit_spec.rb
295
+ - lib/capybara/spec/session/within_frame_spec.rb
291
296
  - lib/capybara/spec/session/within_spec.rb
297
+ - lib/capybara/spec/session/within_window_spec.rb
292
298
  - lib/capybara/spec/session.rb
293
299
  - lib/capybara/spec/test_app.rb
294
300
  - lib/capybara/spec/views/buttons.erb
@@ -310,34 +316,28 @@ files:
310
316
  - lib/capybara/spec/views/within_frames.erb
311
317
  - lib/capybara/spec/views/within_popups.erb
312
318
  - lib/capybara/util/save_and_open_page.rb
313
- - lib/capybara/util/timeout.rb
314
319
  - lib/capybara/version.rb
315
320
  - lib/capybara.rb
316
321
  - spec/basic_node_spec.rb
317
322
  - spec/capybara_spec.rb
318
- - spec/driver/rack_test_driver_spec.rb
319
- - spec/driver/selenium_driver_spec.rb
320
323
  - spec/dsl_spec.rb
321
324
  - spec/fixtures/selenium_driver_rspec_failure.rb
322
325
  - spec/fixtures/selenium_driver_rspec_success.rb
326
+ - spec/rack_test_spec.rb
323
327
  - spec/rspec/features_spec.rb
324
328
  - spec/rspec/matchers_spec.rb
325
329
  - spec/rspec_spec.rb
326
330
  - spec/save_and_open_page_spec.rb
331
+ - spec/selenium_spec.rb
327
332
  - spec/server_spec.rb
328
- - spec/session/rack_test_session_spec.rb
329
- - spec/session/selenium_session_spec.rb
330
333
  - spec/spec_helper.rb
331
- - spec/string_spec.rb
332
- - spec/timeout_spec.rb
333
- - README.rdoc
334
+ - README.md
334
335
  - History.txt
336
+ - License.txt
335
337
  homepage: http://github.com/jnicklas/capybara
336
338
  licenses: []
337
339
  post_install_message:
338
- rdoc_options:
339
- - --main
340
- - README.rdoc
340
+ rdoc_options: []
341
341
  require_paths:
342
342
  - lib
343
343
  required_ruby_version: !ruby/object:Gem::Requirement
@@ -349,12 +349,12 @@ required_ruby_version: !ruby/object:Gem::Requirement
349
349
  required_rubygems_version: !ruby/object:Gem::Requirement
350
350
  none: false
351
351
  requirements:
352
- - - ! '>='
352
+ - - ! '>'
353
353
  - !ruby/object:Gem::Version
354
- version: '0'
354
+ version: 1.3.1
355
355
  requirements: []
356
356
  rubyforge_project: capybara
357
- rubygems_version: 1.8.24
357
+ rubygems_version: 1.8.21
358
358
  signing_key:
359
359
  specification_version: 3
360
360
  summary: Capybara aims to simplify the process of integration testing Rack applications,
@@ -1,722 +0,0 @@
1
- = Capybara
2
-
3
- * http://github.com/jnicklas/capybara
4
-
5
- == Description:
6
-
7
- Capybara aims to simplify the process of integration testing Rack applications,
8
- such as Rails, Sinatra or Merb. Capybara simulates how a real user would
9
- interact with a web application. It is agnostic about the driver running your
10
- tests and currently comes with Rack::Test and Selenium support built in.
11
- HtmlUnit, WebKit and env.js are supported through external gems.
12
-
13
- A complete reference is available at
14
- {at rubydoc.info}[http://rubydoc.info/github/jnicklas/capybara/master].
15
-
16
- == Install:
17
-
18
- Install as a gem:
19
-
20
- sudo gem install capybara
21
-
22
- On OSX you may have to install libffi, you can install it via MacPorts with:
23
-
24
- sudo port install libffi
25
-
26
- == Development:
27
-
28
- * Source hosted at {GitHub}[http://github.com/jnicklas/capybara].
29
- * Please direct questions, discussion or problems to the {mailing list}[http://groups.google.com/group/ruby-capybara].
30
- * If you found a reproducible bug, open a {GitHub Issue}[http://github.com/jnicklas/capybara/issues] to submit a bug report.
31
-
32
- Pull requests are very welcome (and even better than bug reports)! Make sure
33
- your patches are well tested, Capybara is a testing tool after all. Please
34
- create a topic branch for every separate change you make.
35
-
36
- Capybara uses bundler in development. To set up a development environment, simply do:
37
-
38
- git submodule update --init
39
- gem install bundler
40
- bundle install
41
-
42
- == Using Capybara with Cucumber
43
-
44
- Capybara is built to work nicely with Cucumber. Support for Capybara is built into
45
- cucumber-rails. In your Rails app, just run:
46
-
47
- rails generate cucumber:install --capybara
48
-
49
- And everything should be set up and ready to go.
50
-
51
- If you want to use Capybara with Cucumber outside Rails (for example with Merb
52
- or Sinatra), you'll need to require Capybara and set the Rack app manually:
53
-
54
- require 'capybara/cucumber'
55
- Capybara.app = MyRackApp
56
-
57
- Now you can use it in your steps:
58
-
59
- When /I sign in/ do
60
- within("#session") do
61
- fill_in 'Login', :with => 'user@example.com'
62
- fill_in 'Password', :with => 'password'
63
- end
64
- click_link 'Sign in'
65
- end
66
-
67
- Capybara sets up some {tags}[http://wiki.github.com/aslakhellesoy/cucumber/tags]
68
- for you to use in Cucumber. Often you'll want to run only some scenarios with a
69
- driver that supports JavaScript, Capybara makes this easy: simply tag the
70
- scenario (or feature) with <tt>@javascript</tt>:
71
-
72
- @javascript
73
- Scenario: do something Ajaxy
74
- When I click the Ajax link
75
- ...
76
-
77
- You can change which driver Capybara uses for JavaScript:
78
-
79
- Capybara.javascript_driver = :culerity
80
-
81
- There are also explicit <tt>@selenium</tt>, <tt>@culerity</tt> and
82
- <tt>@rack_test</tt> tags set up for you.
83
-
84
- == Using Capybara with RSpec
85
-
86
- If you prefer RSpec to using Cucumber, you can use the built in RSpec support
87
- by adding the following line (typically to your <tt>spec_helper.rb</tt> file):
88
-
89
- require 'capybara/rspec'
90
-
91
- You can now write your specs like so:
92
-
93
- describe "the signup process", :type => :request do
94
- before :each do
95
- User.make(:email => 'user@example.com', :password => 'caplin')
96
- end
97
-
98
- it "signs me in" do
99
- within("#session") do
100
- fill_in 'Login', :with => 'user@example.com'
101
- fill_in 'Password', :with => 'password'
102
- end
103
- click_link 'Sign in'
104
- end
105
- end
106
-
107
- Capybara is only included in example groups tagged with
108
- <tt>:type => :request</tt> (or <tt>:acceptance</tt> for compatibility with Steak).
109
-
110
- If you are testing a Rails app and using the <tt>rspec-rails</tt> gem, these
111
- <tt>:request</tt> example groups may look familiar to you. That's because they
112
- are RSpec versions of Rails integration tests. So, in this case essentially what you are getting are Capybara-enhanced request specs. This means that you can
113
- use the Capybara helpers <i>and</i> you have access to things like named route
114
- helpers in your tests (so you are able to say, for instance, <tt>visit
115
- edit_user_path(user)</tt>, instead of <tt>visit "/users/#{user.id}/edit"</tt>,
116
- if you prefer that sort of thing). A good place to put these specs is
117
- <tt>spec/requests</tt>, as <tt>rspec-rails</tt> will automatically tag them with
118
- <tt>:type => :request</tt>. (In fact, <tt>spec/integration</tt> and
119
- <tt>spec/acceptance</tt> will work just as well.)
120
-
121
- <tt>rspec-rails</tt> will also automatically include Capybara in <tt>:controller</tt> and <tt>:mailer</tt> example groups.
122
-
123
- RSpec's metadata feature can be used to switch to a different driver. Use
124
- <tt>:js => true</tt> to switch to the javascript driver, or provide a
125
- <tt>:driver</tt> option to switch to one specific driver. For example:
126
-
127
- describe 'some stuff which requires js', :js => true do
128
- it 'will use the default js driver'
129
- it 'will switch to one specific driver', :driver => :celerity
130
- end
131
-
132
- Finally, Capybara also comes with a built in DSL for creating descriptive acceptance tests:
133
-
134
- feature "Signing up" do
135
- background do
136
- User.make(:email => 'user@example.com', :password => 'caplin')
137
- end
138
-
139
- scenario "Signing in with correct credentials" do
140
- within("#session") do
141
- fill_in 'Login', :with => 'user@example.com'
142
- fill_in 'Password', :with => 'caplin'
143
- end
144
- click_link 'Sign in'
145
- end
146
- end
147
-
148
- This is, in fact, just a shortcut for making a request spec, where
149
- <tt>feature</tt> is an alias for <tt>describe ..., :type => :request</tt>,
150
- <tt>background</tt> is an alias for <tt>before</tt>, and <tt>scenario</tt>
151
- is an alias for <tt>it</tt>/<tt>specify</tt>.
152
-
153
- Note that Capybara's built in RSpec support only works with RSpec 2.0 or later.
154
- You'll need to roll your own for earlier versions of RSpec.
155
-
156
- == Using Capybara with Test::Unit
157
-
158
- To use Capybara with Test::Unit, include the DSL (<tt>include Capybara</tt> up
159
- until version 0.4.x, <tt>include Capybara::DSL</tt> for newer versions) in
160
- whatever test class you are using. For example, if your classes derive from
161
- <tt>ActionDispatch::IntegrationTest</tt>, use
162
-
163
- class ActionDispatch::IntegrationTest
164
- include Capybara::DSL
165
- end
166
-
167
- Test::Unit does not support selecting the driver through test metadata, but you
168
- can switch the driver for specific classes using the <tt>setup</tt> and
169
- <tt>teardown</tt> methods. See the section "Selecting the Driver".
170
-
171
- == Using Capybara with Ruby on Rails
172
-
173
- If you are using the Rails framework, add this line to automatically configure
174
- Capybara to test against your Rails application:
175
-
176
- require 'capybara/rails'
177
-
178
- == Using Capybara with Rack
179
-
180
- If you're using Capybara with a non-Rails Rack application, set
181
- <tt>Capybara.app</tt> to your application class:
182
-
183
- Capybara.app = MyRackApp
184
-
185
- == Drivers
186
-
187
- Capybara uses the same DSL to drive a variety of browser and headless drivers.
188
-
189
- === Selecting the Driver
190
-
191
- By default, Capybara uses the <tt>:rack_test</tt> driver, which is fast but does not
192
- support JavaScript. You can set up a different default driver for your
193
- features. For example if you'd prefer to run everything in Selenium, you could
194
- do:
195
-
196
- Capybara.default_driver = :selenium
197
-
198
- However, if you are using RSpec or Cucumber, you may instead want to consider
199
- leaving the faster <tt>:rack_test</tt> as the +default_driver+, and marking only those
200
- tests that require a JavaScript-capable driver using <tt>:js => true</tt> or
201
- <tt>@javascript</tt>, respectively. By default, JavaScript tests are run using the
202
- <tt>:selenium</tt> driver. You can change this by setting
203
- <tt>Capybara.javascript_driver</tt>.
204
-
205
- You can also change the driver temporarily (typically in the Before/setup and
206
- After/teardown blocks):
207
-
208
- Capybara.current_driver = :culerity # temporarily select different driver
209
- ... tests ...
210
- Capybara.use_default_driver # switch back to default driver
211
-
212
- Note that switching the driver creates a new session, so you may not be able to
213
- switch in the middle of a test.
214
-
215
- === RackTest
216
-
217
- RackTest is Capybara's default driver. It is written in pure Ruby and does not
218
- have any support for executing JavaScript. Since the RackTest driver works
219
- directly agains the Rack interface, it does not need any server to be started,
220
- it can work directly work against any Rack app. This means that if your
221
- application is not a Rack application (Rails, Sinatra and most other Ruby
222
- frameworks are Rack applications) then you cannot use this driver. You cannot
223
- use the RackTest driver to test a remote application.
224
- {capybara-mechanize}[https://github.com/jeroenvandijk/capybara-mechanize]
225
- intends to provide a similar driver which works against remote servers, it is a
226
- separate project.
227
-
228
- RackTest can be configured with a set of headers like this:
229
-
230
- Capybara.register_driver :rack_test do |app|
231
- Capybara::RackTest::Driver.new(app, :browser => :chrome)
232
- end
233
-
234
- See the section on adding and configuring drivers.
235
-
236
- === Selenium
237
-
238
- At the moment, Capybara supports {Selenium 2.0
239
- (Webdriver)}[http://seleniumhq.org/docs/01_introducing_selenium.html#selenium-2-aka-selenium-webdriver],
240
- *not* Selenium RC. Provided Firefox is installed, everything is set up for you,
241
- and you should be able to start using Selenium right away.
242
-
243
- Capybara can block and wait for Ajax requests to finish after you've interacted
244
- with the page. To enable this behaviour, set the <tt>:resynchronize</tt> driver
245
- option to <tt>true</tt>. This should normally not be necessary, since
246
- Capybara's automatic reloading should take care of any asynchronicity problems.
247
- See the section on Asynchronous JavaScript for details.
248
-
249
- Note: Selenium does not support transactional fixtures; see the section
250
- "Transactional Fixtures" below.
251
-
252
- === HtmlUnit
253
-
254
- There are three different drivers, maintained as external gems, that you can
255
- use to drive {HtmlUnit}[http://htmlunit.sourceforge.net/]:
256
-
257
- * {Akephalos}[https://github.com/bernerdschaefer/akephalos] might be the best
258
- HtmlUnit driver right now.
259
-
260
- * {Celerity}[https://github.com/sobrinho/capybara-celerity] only runs on JRuby,
261
- so you'll need to install the celerity gem under JRuby: <tt>jruby -S gem
262
- install celerity</tt>
263
-
264
- * {Culerity}[https://github.com/sobrinho/capybara-culerity]: Install celerity
265
- as noted above, and make sure that JRuby is in your path. Note that Culerity
266
- does not seem to be working under Ruby 1.9 at the moment.
267
-
268
- Note: HtmlUnit does not support transactional fixtures; see the section
269
- "Transactional Fixtures" below.
270
-
271
- === env.js
272
-
273
- The {capybara-envjs driver}[http://github.com/smparkes/capybara-envjs]
274
- uses the envjs gem ({GitHub}[http://github.com/smparkes/env-js],
275
- {rubygems.org}[http://rubygems.org/gems/envjs]) to interpret
276
- JavaScript outside the browser. The driver is installed by installing the capybara-envjs gem:
277
-
278
- gem install capybara-envjs
279
-
280
- More info about the driver and env.js are available through the links above. The envjs gem only supports
281
- Ruby 1.8.7 at this time.
282
-
283
- Note: Envjs does not support transactional fixtures; see the section
284
- "Transactional Fixtures" below.
285
-
286
- === Capybara-webkit
287
-
288
- The {capybara-webkit drive}[https://github.com/thoughtbot/capybara-webkit] is for true headless
289
- testing. It uses WebKitQt to start a rendering engine process. It can execute JavaScript as well.
290
- It is significantly faster than drivers like Selenium since it does not load an entire browser.
291
-
292
- You can install it with:
293
-
294
- gem install capybara-webkit
295
-
296
- And you can use it by:
297
-
298
- Capybara.javascript_driver = :webkit
299
-
300
-
301
- == The DSL
302
-
303
- Capybara's DSL (domain-specific language) is inspired by Webrat. While
304
- backwards compatibility is retained in a lot of cases, there are certain
305
- important differences. Unlike in Webrat, all searches in Capybara are *case
306
- sensitive*. This is because Capybara heavily uses XPath, which doesn't support
307
- case insensitivity.
308
-
309
- === Navigating
310
-
311
- You can use the
312
- <tt>{visit}[http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Session#visit-instance_method]</tt>
313
- method to navigate to other pages:
314
-
315
- visit('/projects')
316
- visit(post_comments_path(post))
317
-
318
- The visit method only takes a single parameter, the request method is *always*
319
- GET.
320
-
321
- You can get the {current
322
- path}[http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Session#current_path-instance_method]
323
- of the browsing session for test assertions:
324
-
325
- current_path.should == post_comments_path(post)
326
-
327
- === Clicking links and buttons
328
-
329
- <em>Full reference: {Capybara::Node::Actions}[http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Node/Actions]</em>
330
-
331
- You can interact with the webapp by following links and buttons. Capybara
332
- automatically follows any redirects, and submits forms associated with buttons.
333
-
334
- click_link('id-of-link')
335
- click_link('Link Text')
336
- click_button('Save')
337
- click_on('Link Text') # clicks on either links or buttons
338
- click_on('Button Value')
339
-
340
- === Interacting with forms
341
-
342
- <em>Full reference: {Capybara::Node::Actions}[http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Node/Actions]</em>
343
-
344
- There are a number of tools for interacting with form elements:
345
-
346
- fill_in('First Name', :with => 'John')
347
- fill_in('Password', :with => 'Seekrit')
348
- fill_in('Description', :with => 'Really Long Text...')
349
- choose('A Radio Button')
350
- check('A Checkbox')
351
- uncheck('A Checkbox')
352
- attach_file('Image', '/path/to/image.jpg')
353
- select('Option', :from => 'Select Box')
354
-
355
- === Querying
356
-
357
- <em>Full reference: {Capybara::Node::Matchers}[http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Node/Matchers]</em>
358
-
359
- Capybara has a rich set of options for querying the page for the existence of
360
- certain elements, and working with and manipulating those elements.
361
-
362
- page.has_selector?('table tr')
363
- page.has_selector?(:xpath, '//table/tr')
364
- page.has_no_selector?(:content)
365
-
366
- page.has_xpath?('//table/tr')
367
- page.has_css?('table tr.foo')
368
- page.has_content?('foo')
369
-
370
- You can use these with RSpec's magic matchers:
371
-
372
- page.should have_selector('table tr')
373
- page.should have_selector(:xpath, '//table/tr')
374
- page.should have_no_selector(:content)
375
-
376
- page.should have_xpath('//table/tr')
377
- page.should have_css('table tr.foo')
378
- page.should have_content('foo')
379
- page.should have_no_content('foo')
380
-
381
- Note that <tt>page.should have_no_xpath</tt> is preferred over
382
- <tt>page.should_not have_xpath</tt>. Read the section on asynchronous JavaScript
383
- for an explanation.
384
-
385
- If all else fails, you can also use the
386
- <tt>{page.html}[http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Session#html-instance_method]</tt>
387
- method to test against the raw HTML:
388
-
389
- page.html.should match /<span>.../i
390
-
391
- === Finding
392
-
393
- <em>Full reference: {Capybara::Node::Finders}[http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Node/Finders]</em>
394
-
395
- You can also find specific elements, in order to manipulate them:
396
-
397
- find_field('First Name').value
398
- find_link('Hello').visible?
399
- find_button('Send').click
400
-
401
- find(:xpath, "//table/tr").click
402
- find("#overlay").find("h1").click
403
- all('a').each { |a| a[:href] }
404
-
405
- Note that <tt>find</tt> will wait for an element to appear on the page, as explained in the
406
- Ajax section. If the element does not appear it will raise an error.
407
-
408
- These elements all have all the Capybara DSL methods available, so you can restrict them
409
- to specific parts of the page:
410
-
411
- find('#navigation').click_link('Home')
412
- find('#navigation').should have_button('Sign out')
413
-
414
- === Scoping
415
-
416
- Capybara makes it possible to restrict certain actions, such as interacting with
417
- forms or clicking links and buttons, to within a specific area of the page. For
418
- this purpose you can use the generic
419
- <tt>{within}[http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Session#within-instance_method]</tt>
420
- method. Optionally you can specify which kind of selector to use.
421
-
422
- within("li#employee") do
423
- fill_in 'Name', :with => 'Jimmy'
424
- end
425
-
426
- within(:xpath, "//li[@id='employee']") do
427
- fill_in 'Name', :with => 'Jimmy'
428
- end
429
-
430
- Note that <tt>within</tt> will scope the actions to the _first_ (not _any_)
431
- element that matches the selector.
432
-
433
- There are special methods for restricting the scope to a specific fieldset,
434
- identified by either an id or the text of the fieldet's legend tag, and to a
435
- specific table, identified by either id or text of the table's caption tag.
436
-
437
- within_fieldset('Employee') do
438
- fill_in 'Name', :with => 'Jimmy'
439
- end
440
-
441
- within_table('Employee') do
442
- fill_in 'Name', :with => 'Jimmy'
443
- end
444
-
445
- === Scripting
446
-
447
- In drivers which support it, you can easily execute JavaScript:
448
-
449
- page.execute_script("$('body').empty()")
450
-
451
- For simple expressions, you can return the result of the script. Note
452
- that this may break with more complicated expressions:
453
-
454
- result = page.evaluate_script('4 + 4');
455
-
456
- === Debugging
457
-
458
- It can be useful to take a snapshot of the page as it currently is and take a
459
- look at it:
460
-
461
- save_and_open_page
462
-
463
- == Transactional fixtures
464
-
465
- Transactional fixtures only work in the default Rack::Test driver, but not for
466
- other drivers like Selenium. Cucumber takes care of this automatically, but
467
- with Test::Unit or RSpec, you may have to use the
468
- {database_cleaner}[https://github.com/bmabey/database_cleaner] gem. See {this
469
- explanation}[https://groups.google.com/d/msg/ruby-capybara/JI6JrirL9gM/R6YiXj4gi_UJ]
470
- (and code for {solution
471
- 2}[http://opinionated-programmer.com/2011/02/capybara-and-selenium-with-rspec-and-rails-3/#comment-220]
472
- and {solution 3}[http://pastie.org/1745020]) for details.
473
-
474
- == Asynchronous JavaScript (Ajax and friends)
475
-
476
- When working with asynchronous JavaScript, you might come across situations
477
- where you are attempting to interact with an element which is not yet present
478
- on the page. Capybara automatically deals with this by waiting for elements
479
- to appear on the page.
480
-
481
- When issuing instructions to the DSL such as:
482
-
483
- click_link('foo')
484
- click_link('bar')
485
- page.should have_content('baz')
486
-
487
- If clicking on the *foo* link triggers an asynchronous process, such as
488
- an Ajax request, which, when complete will add the *bar* link to the page,
489
- clicking on the *bar* link would be expected to fail, since that link doesn't
490
- exist yet. However Capybara is smart enought to retry finding the link for a
491
- brief period of time before giving up and throwing an error. The same is true of
492
- the next line, which looks for the content *baz* on the page; it will retry
493
- looking for that content for a brief time. You can adjust how long this period
494
- is (the default is 2 seconds):
495
-
496
- Capybara.default_wait_time = 5
497
-
498
- Be aware that because of this behaviour, the following two statements are *not*
499
- equivalent, and you should *always* use the latter!
500
-
501
- page.should_not have_xpath('a')
502
- page.should have_no_xpath('a')
503
-
504
- The former would incorrectly wait for the content to appear, since the
505
- asynchronous process has not yet removed the element from the page, it would
506
- therefore fail, even though the code might be working correctly. The latter
507
- correctly waits for the element to disappear from the page.
508
-
509
- Capybara's waiting behaviour is quite advanced, and can deal with situations
510
- such as the following line of code:
511
-
512
- find('#sidebar').find('h1').should have_content('Something')
513
-
514
- Even if JavaScript causes <tt>#sidebar</tt> to disappear off the page, Capybara
515
- will automatically reload it and any elements it contains. So if an AJAX
516
- request causes the contents of <tt>#sidebar</tt> to change, which would update
517
- the text of the <tt>h1</tt> to "Something", and this happened, this test would
518
- pass. If you do not want this behaviour, you can set
519
- <tt>Capybara.automatic_reload</tt> to <tt>false</tt>.
520
-
521
- == Using the DSL in unsupported testing frameworks
522
-
523
- You can mix the DSL into any context by including +Capybara::DSL+:
524
-
525
-
526
- require 'capybara'
527
- require 'capybara/dsl'
528
-
529
- Capybara.default_driver = :culerity
530
-
531
- module MyModule
532
- include Capybara::DSL
533
-
534
- def login!
535
- within("//form[@id='session']") do
536
- fill_in 'Login', :with => 'user@example.com'
537
- fill_in 'Password', :with => 'password'
538
- end
539
- click_link 'Sign in'
540
- end
541
- end
542
-
543
- == Calling remote servers
544
-
545
- Normally Capybara expects to be testing an in-process Rack application, but you
546
- can also use it to talk to a web server running anywhere on the internets, by
547
- setting app_host:
548
-
549
- Capybara.current_driver = :selenium
550
- Capybara.app_host = 'http://www.google.com'
551
- ...
552
- visit('/')
553
-
554
- Note that the default driver (<tt>:rack_test</tt>) does not support running
555
- against a remote server. With drivers that support it, you can also visit any
556
- URL directly:
557
-
558
- visit('http://www.google.com')
559
-
560
- By default Capybara will try to boot a rack application automatically. You
561
- might want to switch off Capybara's rack server if you are running against a
562
- remote application:
563
-
564
- Capybara.run_server = false
565
-
566
- == Using the sessions manually
567
-
568
- For ultimate control, you can instantiate and use a
569
- {Session}[http://rubydoc.info/github/jnicklas/capybara/master/Capybara/Session]
570
- manually.
571
-
572
- require 'capybara'
573
-
574
- session = Capybara::Session.new(:culerity, my_rack_app)
575
- session.within("//form[@id='session']") do
576
- session.fill_in 'Login', :with => 'user@example.com'
577
- session.fill_in 'Password', :with => 'password'
578
- end
579
- session.click_link 'Sign in'
580
-
581
- == XPath, CSS and selectors
582
-
583
- Capybara does not try to guess what kind of selector you are going to give it,
584
- and will always use CSS by default. If you want to use XPath, you'll need to
585
- do:
586
-
587
- within(:xpath, '//ul/li') { ... }
588
- find(:xpath, '//ul/li').text
589
- find(:xpath, '//li[contains(.//a[@href = "#"]/text(), "foo")]').value
590
-
591
- Alternatively you can set the default selector to XPath:
592
-
593
- Capybara.default_selector = :xpath
594
- find('//ul/li').text
595
-
596
- Capybara allows you to add custom selectors, which can be very useful if you
597
- find yourself using the same kinds of selectors very often:
598
-
599
- Capybara.add_selector(:id) do
600
- xpath { |id| XPath.descendant[XPath.attr(:id) == id.to_s] }
601
- end
602
-
603
- Capybara.add_selector(:row) do
604
- xpath { |num| ".//tbody/tr[#{num}]" }
605
- end
606
-
607
- The block given to xpath must always return an XPath expression as a String, or
608
- an XPath expression generated through the XPath gem. You can now use these
609
- selectors like this:
610
-
611
- find(:id, 'post_123')
612
- find(:row, 3)
613
-
614
- You can specify an optional match option which will automatically use the
615
- selector if it matches the argument:
616
-
617
- Capybara.add_selector(:id) do
618
- xpath { |id| XPath.descendant[XPath.attr(:id) == id.to_s] }
619
- match { |value| value.is_a?(Symbol) }
620
- end
621
-
622
- Now use it like this:
623
-
624
- find(:post_123)
625
-
626
- This :id selector is already built into Capybara by default, so you don't
627
- need to add it yourself.
628
-
629
- == Beware the XPath // trap
630
-
631
- In XPath the expression // means something very specific, and it might not be what
632
- you think. Contrary to common belief, // means "anywhere in the document" not "anywhere
633
- in the current context". As an example:
634
-
635
- page.find(:xpath, '//body').all(:xpath, '//script')
636
-
637
- You might expect this to find all script tags in the body, but actually, it finds all
638
- script tags in the entire document, not only those in the body! What you're looking
639
- for is the .// expression which means "any descendant of the current node":
640
-
641
- page.find(:xpath, '//body').all(:xpath, './/script')
642
-
643
- The same thing goes for within:
644
-
645
- within(:xpath, '//body') do
646
- page.find(:xpath, './/script')
647
- within(:xpath, './/table/tbody') do
648
- ...
649
- end
650
- end
651
-
652
- == Configuring and adding drivers
653
-
654
- Capybara makes it convenient to switch between different drivers. It also exposes
655
- an API to tweak those drivers with whatever settings you want, or to add your own
656
- drivers. This is how to switch the selenium driver to use chrome:
657
-
658
- Capybara.register_driver :selenium do |app|
659
- Capybara::Selenium::Driver.new(app, :browser => :chrome)
660
- end
661
-
662
- However, it's also possible to give this a different name, so tests can switch
663
- between using different browsers effortlessly:
664
-
665
- Capybara.register_driver :selenium_chrome do |app|
666
- Capybara::Selenium::Driver.new(app, :browser => :chrome)
667
- end
668
-
669
- Whatever is returned from the block should conform to the API described by
670
- Capybara::Driver::Base, it does not however have to inherit from this class.
671
- Gems can use this API to add their own drivers to Capybara.
672
-
673
- The {Selenium wiki}[http://code.google.com/p/selenium/wiki/RubyBindings] has
674
- additional info about how the underlying driver can be configured.
675
-
676
- == Gotchas:
677
-
678
- * Access to session and request is not possible from the test, Access to
679
- response is limited. Some drivers allow access to response headers and HTTP
680
- status code, but this kind of functionality is not provided by some drivers,
681
- such as Selenium.
682
-
683
- * Access to Rails specific stuff (such as <tt>controller</tt>) is unavailable,
684
- since we're not using Rails' integration testing.
685
-
686
- * Freezing time: It's common practice to mock out the Time so that features
687
- that depend on the current Date work as expected. This can be problematic,
688
- since Capybara's Ajax timing uses the system time, resulting in Capybara
689
- never timing out and just hanging when a failure occurs. It's still possible to
690
- use plugins which allow you to travel in time, rather than freeze time.
691
- One such plugin is {Timecop}[http://github.com/jtrupiano/timecop].
692
-
693
- * When using Rack::Test, beware if attempting to visit absolute URLs. For
694
- example, a session might not be shared between visits to <tt>posts_path</tt>
695
- and <tt>posts_url</tt>. If testing an absolute URL in an Action Mailer email,
696
- set <tt>default_url_options</tt> to match the Rails default of
697
- <tt>www.example.com</tt>.
698
-
699
- == License:
700
-
701
- (The MIT License)
702
-
703
- Copyright (c) 2009 Jonas Nicklas
704
-
705
- Permission is hereby granted, free of charge, to any person obtaining
706
- a copy of this software and associated documentation files (the
707
- 'Software'), to deal in the Software without restriction, including
708
- without limitation the rights to use, copy, modify, merge, publish,
709
- distribute, sublicense, and/or sell copies of the Software, and to
710
- permit persons to whom the Software is furnished to do so, subject to
711
- the following conditions:
712
-
713
- The above copyright notice and this permission notice shall be
714
- included in all copies or substantial portions of the Software.
715
-
716
- THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND,
717
- EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
718
- MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
719
- IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
720
- CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
721
- TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
722
- SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.