Things on Tech

Background We are in era the of Web, Mobility and AI. Days are gone where we used to think Javascript is just for client side validation check before submitting web forms. Thanks to ECMAScript5 and above which advanced javascript language way forward. Many Enterprises across the world already building applications using lot of opensource Javascript technologies.  Automating the Testing of any web application is becoming challenging and critical for the business. Challenge is in terms of manage and maintain test hygiene throughout the application life cycle and overall product quality. The ideal behavior of any test automation is to be able to integrate as part of CI and CD  (Continuous Deployment)  build and be able to run without manual test run effort and publish test results with code coverage metrics. There are many different frameworks available in the market to solve automation problem. To name few:  CodedUI -  Browser based test automation suite on .net Selenium

ASP.NET.Identity 2.0 is out, and it adds a bunch of great features. – Two-Factor Authentication (SMS, Email or custom) – Account Lockout – Account Confirmation via Email – Password Reset – Sign out everywhere – Choose your Primary Key type (string, int, Guid) – IQuerable Users and Roles – Delete User – Enforcing Unique User Names The upgrade was more fiddly than I thought it would be. Here is what I had to do. I hope it helps. 1. Update Entity Framework to 6.1 2: Update all your OWIN components if they already exist in your project. (Yes. NuGet should handle this for me. It didn’t. Upgrading the Owin components before the Identity packages resolved some issues for me) 3: Update Microsoft ASP.Net Identity Core and then ASP.Net Identity EntityFramework