Eli Weinstock-Herman
"So what do you do?" "I'm lean," "What?", "I'm agile," "What?", "Fine. I make websites."

Continuous Javascript Test Execution with WallabyJS

Original post posted on Thursday, October 13, 2016 at LessThanDot.com

After working with NCrunch building and running tests in the background for the last several years, it feels like something is broken when I have to wait for test results or push a button to start running them. JavaScript runners just didn’t feel like they provided the same level of development feedback, whether they were command-line runners with gulp tasks, plugins like Chutzpah, or dedicated runners like Karma.

I’ve posted previously on both NCrunch and Karma, test runners that run .Net and Javascript code continuously behind the scenes as you develop.

WallabyJS is like NCrunch ...

Continue reading

Stop Manually Updating Your Jasmine SpecRunner

Original post posted on Thursday, October 6, 2016 at LessThanDot.com

I’ve used a number of test frameworks and runners over the years, but my first club out of the bag is still running a SpecRunner file in the browser, with all of the dev tools and console output I’m used to from normal debugging sessions. The painful bit has always been manually keeping the SpecRunner file up to date and forgetting every 3rd or 4th file. Having the SpecRunner is valuable, manually context switching to catch it up over and over is not. So let’s automate it away.

In a prior post, I used gulp to keep my static assets up to date while running a self-hosted...

Continue reading

Self-Hosted Web – Updating assets without restarting the debugger

Original post posted on Friday, July 1, 2016 at LessThanDot.com

When you work with an ASP.Net project through Visual Studio, you can edit static files like CSS and JS files and see them immediately in your browser. Switch to a console application and self-hosted option, such as a self-hosted WebAPI or NancyFX site, and you’ll find that editing Content files will require restarting the debugger to see the changes.

I’ve lived with this in the past, but the regular delay became annoying so I decided to find a solution.


Continue reading

ASP.Net – Single-sign on against Office365 with OAuth2

Original post posted on Friday, June 24, 2016 at LessThanDot.com

Recently I was experimenting with Office 365 as a single-sign on source for an existing ASP.Net application. Unfortunately, most of the documentation I found focused on the use cases of having Visual Studio automatically add it as part of a new project, multiple versions of a very similar looking OWIN sample using built-in (black box) OpenId calls, and using Microsoft.Identity.Clients.ActiveDirectory in not terribly well explained example code to (I think) call the OAuth endpoints.

The examples did not fit well with what I already know about the mechanics of OAuth, so that made it harder to...

Continue reading

Improved TeamCity .Net Build Warnings

Original post posted on Wednesday, June 1, 2016 at LessThanDot.com

A few years back, I posted “Displaying .Net Build Warnings in TeamCity“. Many folks found it useful (and it served as a good reference the last time I needed to re-setup warnings). Recently, Mitch Terlisner reached out to me with a much improved version to share with folks that includes better build status output, an interactive warnings tab, statistics chart, and a custom metric to enable custom failure rules:

Better Warning Output in build status!

Way better (interactive) Warning Output tab!

Build Warnings Statistics Chart!

Custom Failures on Build Warning Count!


Continue reading

Useful Projects