No release in over 3 years
Low commit activity in last 3 years
This gem collects and summarises metrics speficied in the W3C Navigation web performance specifications at http://w3c-test.org/webperf/specs/NavigationTiming/ when using watir and a compatible browser
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 2.0
~> 2.3
~> 1.8
~> 6.2
~> 3.8

Runtime

~> 6.16
 Project Readme

watir-performance¶ ↑

<img src=“https://badge.fury.io/rb/watir-performance.svg” alt=“Gem Version” /> <img src=“https://api.codeclimate.com/v1/badges/ce9c9de5e6146dedab27/maintainability” /> <img src=“https://api.codacy.com/project/badge/Grade/fc700f21a3f446fc8f3b3c2aca400430” alt=“Codacy code quality” /> <img src=“https://travis-ci.org/MacCracken/watir-performance.svg?branch=master” alt=“Build Status” />

Successor to 90kts:watir-webdriver-performance for Watir as opposed to watir-webdriver.

The Watir-Performance aims to provide a set of navigation timing metrics for Watir actions using a W3C page performance standard. This is a perfect solution to capture response time metrics, and it’s very straightforward to do. Works for Chrome, Firefox, Edge and IE9 and up. Currently no Safari support.

This gem collects and summarises metrics speficied in the W3C:Navigation web performance specifications when using watir and a compatible browser.

Example output of browser.performance¶ ↑

All summary times are in milliseconds, and are an abstraction of the w3c web performance specification.

{
  :summary => {
                 :redirect=>0,
                :app_cache=>0,
                      :dns=>0,
          :tcp_connection=>982,
   :tcp_connection_secure=>721,
                :request=>1222,
                  :response=>4,
         :dom_processing=>4293,
          :response_time=>7298,
     :time_to_first_byte=>2205,
      :time_to_last_byte=>2209
  },
  :navigation => {
                   :type => 0,
      :type_back_forward => 2,
         :redirect_count => 0,
          :type_reserved => 255,
          :type_navigate => 0,
            :type_reload => 1
  },
      :memory => {
      :total_js_heap_size => 0,
      :js_heap_size_limit => 0,
       :used_js_heap_size => 0
  },
      :timing => {
                 :domain_lookup_start => 1303180421599,
                      :load_event_end => 0,
                         :connect_end => 1303180421642,
                        :response_end => 1303180421853,
                         :dom_loading => 1303180421840,
                    :navigation_start => 0,
                        :redirect_end => 0,
                  :unload_event_start => 0,
             :secure_connection_start => 0,
                       :connect_start => 1303180421600,
        :dom_content_loaded_event_end => 1303180421934,
                   :domain_lookup_end => 1303180421600,
                     :dom_interactive => 1303180421934,
                    :load_event_start => 0,
                       :request_start => 1303180421642,
                      :response_start => 1303180421838,
                        :dom_complete => 0,
                         :fetch_start => 1303180421598,
      :dom_content_loaded_event_start => 1303180421934,
                      :redirect_start => 0,
                    :unload_event_end => 0
  }
}

Contributing to watir-performance¶ ↑

  • Check out the latest master to make sure the feature hasn’t been implemented or the bug hasn’t been fixed yet

  • Check out the issue tracker to make sure someone already hasn’t requested it and/or contributed it

  • Fork the project

  • Start a feature/bugfix branch

  • Commit and push until you are happy with your contribution

  • Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.

  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright © 2019 Robert MacCracken, 2011 Tim Koopmans

See LICENSE.txt for further details.