wP Utilities

webPageTest utilities

I have found that webPageTest can be unstable on long running CI builds. Sometimes the browsers get stuck etc.

I have designed the jmeter test analysis script to ignore such errors in the calculations and I typically do 3 iterations of a script so I still get good enough timings for my CI purposes. But in order to keep the CI going I have to handle a few error conditions on the test box.

I have a solution that works for me, just to close a couple of Firefox dialog boxes that sometimes pop up on the webpagetest box.

I use autoit3 with a couple of simple scripts that I just start up on the webpagetest box - I compile these scripts into executables and leave them running:

Script 1:

    AutoItSetOption("WinTitleMatchMode", 3)
    while 1=1
    winWait("Firefox","",60)
    if WinExists("Firefox") Then
    WinActivate("Firefox")
    $size = WinGetPos("[active]")
    if($size[2] == 366 And $size[3] == 152) Then
    WinClose("Firefox")

    EndIf
    EndIf
    Wend

Script 2:

    AutoItSetOption("WinTitleMatchMode", 3)
    while 1=1
    winWait("Mozilla Crash Reporter","",60)
    if WinExists("Mozilla Crash Reporter") Then
    WinActivate("Mozilla Crash Reporter")
    WinClose("Mozilla Crash Reporter")
    EndIf
    Wend

 

[Home] [About (CV)] [Contact Us] [JMeter Cloud] [webPageTest] [wP Highlights] [wP Overview] [wP Jenkins] [wp Jmeter] [wP Input] [wP Start] [wP While] [wP Results] [wP Utilities] [_64 images] [asset moniitor] [Linux Monitor] [Splunk ETL] [Splunk API] [AWS bash] [LR Rules OK] [LR Slave] [LR CI Graphs] [LoadRunner CI] [LR CI Variables] [LR Bamboo] [LR Methods] [LR CI BASH] [Bash methods] [Jenkins V2] [Streaming vid] [How fast] [Finding Issues] [Reporting] [Hand over] [VB Scripts] [JMeter tips] [JMeter RAW] [Dynatrace] [Documents] [FAQ] [Legal]

In the Cartesian Elements Ltd group of companies