rails

History

Edouard CHIN 01a26e581f Implement a way to add browser capabilities: * There is currently no way to define specific browser capabilities since our SystemTest driver override the `option` key [Ref](`a07d068078/actionpack/lib/action_dispatch/system_testing/driver.rb (L35)`) This option key is used internally by selenium to add custom capabilities on the browser. Depending on the Browser, some option are allowed to be passed inside a hash, the driver takes care of setting whatever you passed on the driver option. An example [here](`a07d068078/actionpack/lib/action_dispatch/system_testing/driver.rb (L35)`) where you are allowed to pass args such as `--no-sandbox` etc However this behavior was only meant for backward compatibility and as you can see it's deprecated. The non-deprecated behavior is to create a `<Driver>::Option` object containing all the capabilities we want. This is what we [currently do](`a07d068078/actionpack/lib/action_dispatch/system_testing/browser.rb (L34-L36)`) when chrome or firefox are in headless mode. This PR allows to pass a block when calling `driven_by`, the block will be pased a `<Driver>::Option` instance. You can modify this object the way you want by adding any capabilities. The option object will be then passed to selenium. ```ruby driven_by :selenium, using: :chrome do \|driver_option\| driver_option.add_argument('--no-sandbox') driver_option.add_emulation(device: 'iphone 4') end ```		2019-01-29 08:50:29 -05:00
..
bin	Use frozen string literal in actionpack/	2017-07-29 14:02:40 +03:00
lib	Implement a way to add browser capabilities:	2019-01-29 08:50:29 -05:00
test	Implement a way to add browser capabilities:	2019-01-29 08:50:29 -05:00
actionpack.gemspec	Require Ruby 2.5 for Rails 6.	2018-12-19 21:47:50 +01:00
CHANGELOG.md	Implement a way to add browser capabilities:	2019-01-29 08:50:29 -05:00
MIT-LICENSE	Bump license years for 2019	2018-12-31 10:24:38 +07:00
Rakefile	Improve redundancy in line tasks	2018-04-19 23:45:28 +09:00
README.rdoc	Fix typos and add a few suggestions	2017-11-28 19:27:43 +01:00

README.rdoc

= Action Pack -- From request to response

Action Pack is a framework for handling and responding to web requests. It
provides mechanisms for *routing* (mapping request URLs to actions), defining
*controllers* that implement actions, and generating responses by rendering
*views*, which are templates of various formats. In short, Action Pack
provides the view and controller layers in the MVC paradigm.

It consists of several modules:

* Action Dispatch, which parses information about the web request, handles
  routing as defined by the user, and does advanced processing related to HTTP
  such as MIME-type negotiation, decoding parameters in POST, PATCH, or PUT bodies,
  handling HTTP caching logic, cookies and sessions.

* Action Controller, which provides a base controller class that can be
  subclassed to implement filters and actions to handle requests. The result
  of an action is typically content generated from views.

With the Ruby on Rails framework, users only directly interface with the
Action Controller module. Necessary Action Dispatch functionality is activated
by default and Action View rendering is implicitly triggered by Action
Controller. However, these modules are designed to function on their own and
can be used outside of Rails.


== Download and installation

The latest version of Action Pack can be installed with RubyGems:

  $ gem install actionpack

Source code can be downloaded as part of the Rails project on GitHub:

* https://github.com/rails/rails/tree/master/actionpack


== License

Action Pack is released under the MIT license:

* https://opensource.org/licenses/MIT


== Support

API documentation is at:

* http://api.rubyonrails.org

Bug reports for the Ruby on Rails project can be filed here:

* https://github.com/rails/rails/issues

Feature requests should be discussed on the rails-core mailing list here:

* https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-core