This talk captures the learnings from running the CodeLens service in Visual Studio Online. We used data extensively and benefited from the overall learnings in Visual Studio Online and its component micro-services.

I have attached a deck with the outline of the presentation. Please review it and vote for my session if you like it.

Data @ the core of Enterprise Agile.pptx

In fact, we have been incrementally releasing features over the past few months.  Here are a bunch of blogs which discuss the new features.

MSBuild and Team Foundation Server integration with SonarQube: version 1.0 released

Build Tasks for SonarQube Analysis

I have also proposed a session at the Agile India conference - Beyond the wall of Issues. See the attached deck which I am proposing to present.

Beyond the wall of issues.pptx

Here are tweets 11-20.

Tweet #11 : #VisualStudio #CodeLens Test Indicators helps identify and run unit tests which test the current code element.

Tweet #12 : #VisualStudio #CodeLens details has an icon next to each change. The icon shows where the change came from.

Tweet #13 : #VisualStudio #CodeLens allows you to visualize references on a CodeMap.

Tweet #14 : #VisualStudio #CodeLens processing in Team Foundation Server can be managed using TFSConfig CodeIndex command - http://msdn.microsoft.com/en-us/library/dn280925.aspx …

Tweet #15 :  #VisualStudio #CodeLens color & font can be changed from Tools, Options, Environment, Fonts and Colors.

Tweet #16 : You can preview the referencing code from #VisualStudio #CodeLens by moving your mouse over any reference.

Tweet #17 : #Visual Studio #CodeLens has been integrated with Code Map to navigate the diagnostics data in exceptions. http://blogs.msdn.com/b/visualstudioalm/archive/2014/03/07/enhancements-to-debugging-exceptions-with-intellitrace-in-visual-studio-2013.aspx …

Tweet #18 : You can find when a code element was last changed in #VisualStudio #CodeLens Authors Indicator.

Tweet #19 : Steven Lange wrote this great article talking about the value of #VisualStudio #CodeLens - http://blogs.msdn.com/b/slange/archive/2014/06/17/panels-vs-context-a-tale-of-two-visual-studios-and-a-practical-explanation-of-the-value-of-codelens.aspx …

Tweet #20 : #VisualStudio #CodeLens Changes indicator shows if you have an old version of code element/file-See +1 below.

Tweets 1-10 are listed here.

Here are the past tweets.

Tweet #1 : Starting a tweet series on #VisualStudio #CodeLens - CodeLens Introduction in MSDN-msdn.microsoft.com/en-us/library/… pic.twitter.com/p5ybVHkduJ

Tweet #3 : #VisualStudio #CodeLens Team Indicators (Authors, Changes, Bugs, Workitems & Code Reviews) are retrieved from TFS when a file is opened.

Tweet #4 : #VisualStudio #CodeLens Team Indicators are refreshed automatically every 15mins. You can refresh the indicators from context menu also.

Tweet #5 :  #VisualStudio #CodeLens Authors indicator makes it super-easy to identify an expert who can answer a query on the current code element.

Tweet #6 : #VisualStudio #CodeLens has built in Outlook & Lync integration. Right click on any author to start a conversation.

Tweet #7 : #VisualStudio #CodeLens provides info for each code element. An author is listed for a method only if she has modified it.

Tweet #8 : #VisualStudio #CodeLens Team Indicators are available for Team Foundation Version Control & Git - blogs.msdn.com/b/visualstudio…

Tweet #9 : #VisualStudio #CodeLens Team Indicators for Git are computed on the client. They are available for any Git repo - local, TfGit, GitHub.

Tweet #10 :  #VisualStudio #CodeLens Incoming Changes indicator gives you information about changes made in other branches. pic.twitter.com/34nHzgjaZg

Problem Statement

Several customers have a few code files (in most cases tool-generated) which have a large number of code elements and are changed frequently. The CodeLens files for such files will be very large. Processing these files takes time and thus increases the duration of CodeLens jobs. In addition, Processing these files are CPU intensive too.  Since developers don’t look at these files at all (they look at the original file from which these are generated), it is acceptable to ignore them from CodeLens processing.  We received requests from these customers to allow them to list these large files and ignore them from CodeLens processing.

New Feature – List Large Files

In Visual Studio 2013 Update 3, we have enhanced the command line utility (described in this MSDN article - CodeIndex Command), to list large files.

TfsConfig codeIndex /listLargeFiles [/fileCount:<FileCount>]  [/minSize:<MinSize>] /collectionName:<CollectionName> | /collectionId:<CollectionId>]

Display large Files.

EXAMPLE

TfsConfig codeIndex /listLargeFiles /fileCount:50 /minSize:10 /collectionName:<CollectionName>

Display 50 files that are larger than 10 KB.

(Note that the CodeLens files are compressed and the file size shown here is after compression).

After getting the list of large files, TFS administrators can add them to ignored list using TFSConfig CodeIndex /ignoreList:add.

Summary

In this blog post, I talked about a new feature to list large files that can be used by Team Foundation Server administrators to enable them to optimize CodeLens job processing. As always, looking forward to your feedback and questions on this topic and CodeLens in general.

Visual Studio 2012 Update 2

Download and Install	Visual Studio 2012 Update 2 CTP 3
Blogs	Introducing JavaScript Execution on InternetExplorer and CrossBrowser in Coded UI Test Introducing window based smart match for Cross Browser Testing with Coded UI Test UI Testing of Microsoft SharePoint 2013 with Visual Studio 2012

Visual Studio 2012 Update 1

Download and Install	Visual Studio 2012 Update 1
Features	Using Different Web Browsers with Coded UI Tests
Blogs	Introducing Cross Browser Testing with Coded UI Tests Troubleshooting tips for cross browser testing in Coded UI Test Retrying failed playback actions with Coded UI Coded UI Test: Configuring Search Properties while recording on Internet Explorer Coded UI Test Support Matrix (updated Oct 2012)
Videos	Record on IE and Playback everywhere Author cross browser tests with Coded UI Test Builder Author cross browser tests using plain hand coding without UI Map Run cross browser tests sequentially on multiple browsers Troubleshoot cross browser test failures

Visual Studio 2012

I have uploaded a project template on Visual Studio Gallery to enable QUnit Tests on Metro style apps built  using Html/Javascript. You can download it here. After installing this project template (and restarting Visual Studio), you can choose New Project -> Javascript -> QUnit Test for Metro Style Apps. You can hit F5 now to run the sample tests and see the results.

Metro style apps run in an an app container that restricts the capabilities of application. This is intended to protect the user from malicious apps. In order to run QUnit Tests inside the app container, I have made one change in qunit.js (added a window.toStaticHtml around the banner innerHtml). In addition, please note that I have added two capabilities in the appxmanifest [for Internet(client) and Document Library access]. These capabilities are used in my sample Metro style tests.

The sample tests are defined in the file tests.js in the js folder. There are 5 sample tests already defined for your reference.

I built this project template by starting from a Blank App and adding the required qunit files.

1. qunit.css in css folder
2. qunit.js and tests.js in js folder
3. default.html in the project root folder (content updated)

Asynchronous calls in C++ Windows Store Unit Tests

Publishing test results through command line test runner

How to manage unit tests in Visual Studio 2012 Update 1 : Part 1–Using Traits in the Unit Test Explorer

Part 2–Using Traits with different test frameworks in the Unit Test Explorer

Implementing Traits in custom Visual Studio Test Adapters 

Introducing SharePoint Emulators

Writing a Visual Studio 2012 Unit Test Adapter

Anatomy of a File-based Unit Test Plugin

Authoring a new Visual studio unit test adapter

How to make your extension visible to the test explorer in Visual Studio 11?

Writing loggers for command line test runner vstest.console.exe

How to enable UTE logs?

Running Windows 8 Metro style tests in TeamBuild

How to write tests in WinRT Component DLL project [for VS11 Beta/Consumer Preview]

Running Unit Tests for Windows Metro style apps from Command Line

Visual Studio 11 Fakes Part 1 - Stubs

Visual Studio Fakes Part 2 – Shims

Why mstest did not deploy my deployment item?

Ordered test timeout

TestContext folders explained

Visual Studio 2012 RC – What’s new in Unit Testing

What’s New in Visual Studio 11 Beta Unit Testing

What’s new for MSTest unit tests in Visual Studio 11 Beta

Visual Studio 11 Beta - Unit Testing Plugins List

http://xunit.codeplex.com/

http://nunit.org/

https://github.com/Gallio/Gallio-VS2011-Integration

http://chutzpah.codeplex.com/

Javascript Unit Tests on Team Foundation Service with Chutzpah

QUnit Tests for Metro Style Apps

Vikram Agarwal

Bhuvaneshwari K

Peter Provost

Aseem Bansal 

The Three Rules Of Tdd

Kata - the Only Way to Learn TDD

The Bowling Game Kata

The Prime Factors Kata

TDD Fluency

TDD Apostate

TDD Zealot

Unit Testing ASP.NET Web API

 Mocks Aren’t Stubs

How I Learned to Stop Worrying and Love the Mock

Mock Free Example, Part 1: Project Intro

Mock Free Example, part 2: Simulators

Mock Free Example, Part 3: Fixing Untestable Code Sequences

Simulating the File System

New Simulators Library

Decoupled Design

When you record actions & generate code in Coded UI Test, you get actions like

Mouse.Click(uISearchButton, new Point(18, 15));

Many users are confused by the Point argument we pass to Mouse.Click and believe that we are doing a coordinate based action here. The Point argument here is relative to the button itself. So test will not fail if the button moves around in the page. More importantly, you can completely remove the Point argument. The code could be written as

Mouse.Click(uISearchButton);

This will still work. If no Point argument is specified, Visual Studio UI Test Framework determines a clickable point and performs the click on that point.

Why do you then keep coordinates? Remove them!!

There are specific scenarios where these coordinates really come in handy.

Consider a DropDownButton, which drops down when you click on the expander arrow. If you click on the button’s normal area, it is invoked. If you click on the expander, it shows the additional buttons and you can click on one of them. Since we record relative coordinates for the click action, we can playback the actions on the expander also. If we had not recorded coordinates and clicked on the first available clickable point in the button, this scenario would have failed.

e.g:- Look at the screenshot below.

Here I am clicking on the expander in Picture Button to bring up additional options. This scenario will only work if we record relative coordinates on the click action.