Category: Useful tool

BenchmarkDotNet

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

Wfetch is originally part of the IIS 6.0 Resource Kit Tools.
It can be used to troubleshoot http redirects, http status codes etc.

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 Download.com

More info:
https://support.microsoft.com/en-in/help/284285/how-to-use-wfetch-exe-to-troubleshoot-http-connections

 

Report tools for NUnit xml test report file

I have recently been doing custom Powershell script steps for Octopus deploy to trigger Selenium based UI tests and needed a good way to present the test outcome.

This command line tool creates a nice html dashboard page of the xml:

ReportUnit
https://github.com/reportunit/reportunit
Support for both NUnit 2.x, 3.x and MSTest

Interesting alternatives:

NUnit HTML Report Generator
https://github.com/SongArc/NUnit-HTML-Report-Generator/blob/master/README.md

NUnit Test Results Viewer
‘NUnit Test Results Viewer’ is a free open source project that allows to view NUnit resulted *xml file.
https://sourceforge.net/projects/nunittrviewer/

If tests are triggered from TeamCity or VSTS (Visual Studio Team Services) they have test report tools built-in.

Cashew: A simple and elegant yet powerful HTTP client cache for .NET

A simple and elegant yet powerful HTTP client cache for .NET

Cashew

Cashew is a .NET library for caching responses easily with an HttpClient through an API that is simple and elegant yet powerful. There’s support out of the box for the awesome CacheManager via the Cashew.Adapters.CacheManager package. Its aim is to focus on the HTTP part of caching and not worrying about how stuff is stored, meaning no half-arsed cache implementations!

Cashew targets .NET 4.5 and .NET Standard 1.1 (.NET Core, Mono, Xamarin.iOS, Xamarin.Android, UWP and more) meaning it can be used on all sorts of devices.

Source: joakimskoog/Cashew: A simple and elegant yet powerful HTTP client cache for .NET

ReportUnit – xml testresult to html dashboard tool

ReportUnit is a report generator for the test-runner family. It uses stock reports from NUnit, MSTest and Gallio and converts them into attractive HTML reports with dashboards.

Works with nUnit 3.x as well.

Nuget: https://www.nuget.org/packages/ReportUnit/

Github: https://github.com/reportunit/reportunit

Visual Studio Toolkit – Visual Studio 2015/2017 Extension

Great small extension for the following functionality:

  • Select 2 files in Solution Explorer, right click and new menu option at the top “Compare files”.
  • Right click solution or a project, new menu option at the top “Edit Solution/Project file”
  • Locate File in Solution Explorer / Source Control explorer (right click menu on tab in code edit window)

Source: Visual Studio Toolkit – Visual Studio Marketplace

Visual Studio Window Title Changer Extension

https://marketplace.visualstudio.com/items?itemName=IstvanPasztor.VisualStudioWindowTitleChanger

Changes the Visual Studio Window Title by evaluating a user defined expression. Extremely helpful when working with multiple branches of the same project.

Script I use to see current branch in TFS (path) or GIT (git branch) in title:

if( sln_open ) {
if (exec git_branch 2 "git rev-parse --abbrev-ref HEAD" sln_dir) {
//GIT
sln_filename + (exec git_branch 2 "git rev-parse --abbrev-ref HEAD" sln_dir ? " - git["+git_branch+"]" + " - Visual Studio 2015")
} 
else 
{ 
//TFS or Standard project
sln_filename + " - (" + sln_dir +")" + " - " + "Visual Studio 2015"
} 
}
else {
//No solution open
"Visual Studio 2015"
}