Why the statistics data is no wrong when enable the autologin plugin

drewz's Avatar


28 Sep, 2014 08:02 AM

when enable the autologin plugin the statistics data is always show below:

     {:http=>{:request_count=>3, :response_count=>3, :time_out_count=>0, :total_responses_per_second=>3.185826047526153, :burst_response_time_sum=>3.167599, :burst_response_count=>3, :burst_responses_per_second=>0.9179918133490085, :burst_average_response_time=>1.0558663333333334, :total_average_response_time=>1.0558663333333334, :max_concurrency=>20}, :runtime=>4.271384, :found_pages=>0, :audited_pages=>0, :current_page=>""}_page=>""}}

disable autologin plugin is work well:

   {:http=>{:request_count=>37, :response_count=>24, :time_out_count=>0, :total_responses_per_second=>34.640782304333705, :burst_response_time_sum=>11.590416000000001, :burst_response_count=>22, :burst_responses_per_second=>18.333990301319133, :burst_average_response_time=>0.5268370909090909, :total_average_response_time=>0.5384198750000001, :max_concurrency=>20}, :runtime=>1.994631, :found_pages=>1, :audited_pages=>1, :current_page=>"http://www.testfire.net/search.aspx"}
  1. Support Staff 1 Posted by Tasos Laskos on 28 Sep, 2014 08:08 AM

    Tasos Laskos's Avatar

    What makes you think they're wrong? The autologin plugin will pause the system while it logs in, so if you grab the stats at that moment you'll see less progress than when the auologin plugin is not enabled.

  2. 2 Posted by drewz on 28 Sep, 2014 08:57 AM

    drewz's Avatar

    my means after success log in statistics data. from success log in to complete scan , the statistics data no any change.always display like below {:http=>{:request_count=>3, :response_count=>3, :time_out_count=>0, :total_responses_per_second=>3.185826047526153, :burst_response_time_sum=>3.167599, :burst_response_count=>3, :burst_responses_per_second=>0.9179918133490085, :burst_average_response_time=>1.0558663333333334, :total_average_response_time=>1.0558663333333334, :max_concurrency=>20}, :runtime=>4.271384, :found_pages=>0, :audited_pages=>0, :current_page=>""}_page=>""}}
    from pause direct to finish, no implement any check

  3. Support Staff 3 Posted by Tasos Laskos on 28 Sep, 2014 09:01 AM

    Tasos Laskos's Avatar

    Are you sure it logs in successfully? If that autologin plugin does not un-pause the system that means that the login failed.

    Can you show me your code please?

  4. 4 Posted by drewz on 29 Sep, 2014 07:32 AM

    drewz's Avatar

    sorry, find root cause, after use 1.0.2 not success log in.
    because below code in autologin.rb, in our web site no redirect, so the response.url
    is same to @url = options[:url].to_s and return false for "session.logged_in"
    framework.options.session.check_url = response.url framework.options.session.check_pattern = @verifier if !session.logged_in? register_results( 'status' => 'check_failed', 'message' => STATUSES[:check_failed] ) print_error STATUSES[:check_failed] @errored = true return end

  5. Support Staff 5 Posted by Tasos Laskos on 29 Sep, 2014 07:36 AM

    Tasos Laskos's Avatar

    Ah, OK. This issue has been fixed and will be in the next bugfix release. The autologin plugin will use the global settings if they have been set.

    You can verify this using the experimental branch if you wish.


  6. Tasos Laskos closed this discussion on 29 Sep, 2014 07:36 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac