[Live Now] Join the 1-day Testing & QA Summit featuring 15+ Expert Speakers.Join for FREE! Join TestMu Conference

How to use finish method of ActiveSupport Package

Best Test-prof_ruby code snippet using ActiveSupport.finish

notifications.rb

Source:notifications.rb

...27  #28  # You can consume those events and the information they provide by registering29  # a subscriber.30  #31  #   ActiveSupport::Notifications.subscribe('render') do |name, start, finish, id, payload|32  #     name    # => String, name of the event (such as 'render' from above)33  #     start   # => Time, when the instrumented block started execution34  #     finish  # => Time, when the instrumented block ended execution35  #     id      # => String, unique ID for the instrumenter that fired the event36  #     payload # => Hash, the payload37  #   end38  #39  # Here, the +start+ and +finish+ values represent wall-clock time. If you are40  # concerned about accuracy, you can register a monotonic subscriber.41  #42  #   ActiveSupport::Notifications.monotonic_subscribe('render') do |name, start, finish, id, payload|43  #     name    # => String, name of the event (such as 'render' from above)44  #     start   # => Monotonic time, when the instrumented block started execution45  #     finish  # => Monotonic time, when the instrumented block ended execution46  #     id      # => String, unique ID for the instrumenter that fired the event47  #     payload # => Hash, the payload48  #   end49  #50  # The +start+ and +finish+ values above represent monotonic time.51  #52  # For instance, let's store all "render" events in an array:53  #54  #   events = []55  #56  #   ActiveSupport::Notifications.subscribe('render') do |*args|57  #     events << ActiveSupport::Notifications::Event.new(*args)58  #   end59  #60  # That code returns right away, you are just subscribing to "render" events.61  # The block is saved and will be called whenever someone instruments "render":62  #63  #   ActiveSupport::Notifications.instrument('render', extra: :information) do64  #     render plain: 'Foo'65  #   end66  #67  #   event = events.first68  #   event.name      # => "render"69  #   event.duration  # => 10 (in milliseconds)70  #   event.payload   # => { extra: :information }71  #72  # The block in the <tt>subscribe</tt> call gets the name of the event, start73  # timestamp, end timestamp, a string with a unique identifier for that event's instrumenter74  # (something like "535801666f04d0298cd6"), and a hash with the payload, in75  # that order.76  #77  # If an exception happens during that particular instrumentation the payload will78  # have a key <tt>:exception</tt> with an array of two elements as value: a string with79  # the name of the exception class, and the exception message.80  # The <tt>:exception_object</tt> key of the payload will have the exception81  # itself as the value:82  #83  #   event.payload[:exception]         # => ["ArgumentError", "Invalid value"]84  #   event.payload[:exception_object]  # => #<ArgumentError: Invalid value>85  #86  # As the earlier example depicts, the class <tt>ActiveSupport::Notifications::Event</tt>87  # is able to take the arguments as they come and provide an object-oriented88  # interface to that data.89  #90  # It is also possible to pass an object which responds to <tt>call</tt> method91  # as the second parameter to the <tt>subscribe</tt> method instead of a block:92  #93  #   module ActionController94  #     class PageRequest95  #       def call(name, started, finished, unique_id, payload)96  #         Rails.logger.debug ['notification:', name, started, finished, unique_id, payload].join(' ')97  #       end98  #     end99  #   end100  #101  #   ActiveSupport::Notifications.subscribe('process_action.action_controller', ActionController::PageRequest.new)102  #103  # resulting in the following output within the logs including a hash with the payload:104  #105  #   notification: process_action.action_controller 2012-04-13 01:08:35 +0300 2012-04-13 01:08:35 +0300 af358ed7fab884532ec7 {106  #      controller: "Devise::SessionsController",107  #      action: "new",108  #      params: {"action"=>"new", "controller"=>"devise/sessions"},109  #      format: :html,110  #      method: "GET",111  #      path: "/login/sign_in",112  #      status: 200,113  #      view_runtime: 279.3080806732178,114  #      db_runtime: 40.053115  #    }116  #117  # You can also subscribe to all events whose name matches a certain regexp:118  #119  #   ActiveSupport::Notifications.subscribe(/render/) do |*args|120  #     ...121  #   end122  #123  # and even pass no argument to <tt>subscribe</tt>, in which case you are subscribing124  # to all events.125  #126  # == Temporary Subscriptions127  #128  # Sometimes you do not want to subscribe to an event for the entire life of129  # the application. There are two ways to unsubscribe.130  #131  # WARNING: The instrumentation framework is designed for long-running subscribers,132  # use this feature sparingly because it wipes some internal caches and that has133  # a negative impact on performance.134  #135  # === Subscribe While a Block Runs136  #137  # You can subscribe to some event temporarily while some block runs. For138  # example, in139  #140  #   callback = lambda {|*args| ... }141  #   ActiveSupport::Notifications.subscribed(callback, "sql.active_record") do142  #     ...143  #   end144  #145  # the callback will be called for all "sql.active_record" events instrumented146  # during the execution of the block. The callback is unsubscribed automatically147  # after that.148  #149  # To record +started+ and +finished+ values with monotonic time,150  # specify the optional <tt>:monotonic</tt> option to the151  # <tt>subscribed</tt> method. The <tt>:monotonic</tt> option is set152  # to +false+ by default.153  #154  #   callback = lambda {|name, started, finished, unique_id, payload| ... }155  #   ActiveSupport::Notifications.subscribed(callback, "sql.active_record", monotonic: true) do156  #     ...157  #   end158  #159  # === Manual Unsubscription160  #161  # The +subscribe+ method returns a subscriber object:162  #163  #   subscriber = ActiveSupport::Notifications.subscribe("render") do |*args|164  #     ...165  #   end166  #167  # To prevent that block from being called anymore, just unsubscribe passing168  # that reference:169  #170  #   ActiveSupport::Notifications.unsubscribe(subscriber)171  #172  # You can also unsubscribe by passing the name of the subscriber object. Note173  # that this will unsubscribe all subscriptions with the given name:174  #175  #   ActiveSupport::Notifications.unsubscribe("render")176  #177  # Subscribers using a regexp or other pattern-matching object will remain subscribed178  # to all events that match their original pattern, unless those events match a string179  # passed to `unsubscribe`:180  #181  #   subscriber = ActiveSupport::Notifications.subscribe(/render/) { }182  #   ActiveSupport::Notifications.unsubscribe('render_template.action_view')183  #   subscriber.matches?('render_template.action_view') # => false184  #   subscriber.matches?('render_partial.action_view') # => true185  #186  # == Default Queue187  #188  # Notifications ships with a queue implementation that consumes and publishes events189  # to all log subscribers. You can use any queue implementation you want.190  #191  module Notifications192    class << self193      attr_accessor :notifier194      def publish(name, *args)195        notifier.publish(name, *args)196      end197      def instrument(name, payload = {})198        if notifier.listening?(name)199          instrumenter.instrument(name, payload) { yield payload if block_given? }200        else201          yield payload if block_given?202        end203      end204      # Subscribe to a given event name with the passed +block+.205      #206      # You can subscribe to events by passing a String to match exact event207      # names, or by passing a Regexp to match all events that match a pattern.208      #209      #   ActiveSupport::Notifications.subscribe(/render/) do |*args|210      #     @event = ActiveSupport::Notifications::Event.new(*args)211      #   end212      #213      # The +block+ will receive five parameters with information about the event:214      #215      #   ActiveSupport::Notifications.subscribe('render') do |name, start, finish, id, payload|216      #     name    # => String, name of the event (such as 'render' from above)217      #     start   # => Time, when the instrumented block started execution218      #     finish  # => Time, when the instrumented block ended execution219      #     id      # => String, unique ID for the instrumenter that fired the event220      #     payload # => Hash, the payload221      #   end222      #223      # If the block passed to the method only takes one parameter,224      # it will yield an event object to the block:225      #226      #   ActiveSupport::Notifications.subscribe(/render/) do |event|227      #     @event = event228      #   end229      def subscribe(pattern = nil, callback = nil, &block)230        notifier.subscribe(pattern, callback, monotonic: false, &block)231      end232      def monotonic_subscribe(pattern = nil, callback = nil, &block)...

Automation Testing Tutorials

Learn to execute automation testing from scratch with LambdaTest Learning Hub. Right from setting up the prerequisites to run your first automation test, to following best practices and diving deeper into advanced test scenarios. LambdaTest Learning Hubs compile a list of step-by-step guides to help you be proficient with different test automation frameworks i.e. Selenium, Cypress, TestNG etc.