Benchmarking is really hard (especially microbenchmarking), you can easily make a mistake during performance measurements. BenchmarkDotNet will protect you from the common pitfalls (even for experienced developers) because it does all the dirty work for you: it generates an isolated project per each benchmark method, does several launches of this project, run multiple iterations of the method (include warm-up), and so on. Usually, you even shouldn’t care about a number of iterations because BenchmarkDotNet chooses it automatically to achieve the requested level of precision.

Source: Home – BenchmarkDotNet Documentation

WFetch – Simple Microsoft Tool for troubleshooting HTTP connections

This simple but powerful testing tool is a must-have for any system administrator or Web site manager. Wfetch’s simple GUI offers easy input and clear output to test almost any Web host. Don’t expect a manual or clear failure information. This tool was released for expert users.Operating Wfetch is actually very simple, providing you understand Web functions such as Get, Put, Head, Trace, Post, and others. It’s a mere matter of using a few pull-downs, entering some simple text and pressing Go. The trick comes when users must interpret the Log Output from their commands. If Get HTTP/1.1\r\n makes sense, this app was written for you. The utility offers numerous authentication and connection features. Additional commands make it easy to copy and paste text from the output log file.Wfetch is not secure as it stores user names and passwords in plain text. Nevertheless, it is an invaluable freeware tool for any user looking to diagnosis certain connection problems.

Source: WFetch – Free download and software reviews – CNET

Its originally part of the IIS 6.0 Resource Kit Tools.

More info:


How To Automatically Retry Failed Tests in Nunit

If you have some randomly failing tests, such as Selenium driver based tests and are using Nunit as testing framework, here is one way to enable automatic re-run of the those failing tests. (Works with Nunit 3+ adding a custom method attribute)

Source: How To Automatically Retry Failed Tests in Nunit – Testing repository

Problem with remote Selenium IE driver “Unable to find element with css selector”

Running my Selenium tests locally against IE11 works fine, but when calling remote Selenium server running the same browser and Selenium drivers setup I get this:

The problem is connected to the fact that the IEDriverServer.exe runs the server IE11 version. In my case this is a Windows Server 2016 which has a higher security restriction.

For me the solution was to disable the Internet Explorer Enhanced Security Configuration. Follow this guide for the Windows Server 2016 version.

Disable Internet Explorer Enhanced Security Configuration in Windows Server 2016

The same error could also be caused by javascript not enabled for the driver:

or need driver to switch to the correct frame/window

More info here:

Powershell Generic Invoke-RestMethod / WebRequest error handler


Then, wrap all of your Invoke-RestMethod calls in a try Catch block like this.

Now when you run into an error, you can see the actual message, like this