We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of review of the problem with estimation in projects today and then an overview of the concept of agile estimation and the notion of re–estimation. Read more
Continuous Integration and scheduled builds are an important part of any development process. To get the best out of these tools, as much testing as possible should be wired into the post build process. With the 2010 release of Visual Studio we get the Lab Manager product that allows us to deploy our automated build to a virtualised test environment for either manual and?or automated testing. This session presents an end to end demo, showing how an application can be build, deployed and tested with the Lab Manager environment.
Behavior-Driven Development is more than a technique for creating and organizing unit tests. It is also a wonderful way to communicate with customers and users about the software being created. This video demonstrates some techniques and tools you can use to start delivering software with BDD. : Using Behavior-Driven Development frameworks, this session explores ways to create software starting with solid Agile requirements, moving all the way through automated testing. We use .NET in C# and Visual Studio ALM, although none of these exact tools are required to accomplish the goals we set forth.
Scrum for Team System v3 significantly evolves the leading Scrum process template by leveraging the capabilities of Visual Studio Team System 2010 Team Foundation Server (TFS 2010) to enhance the support for Agile best practices. Hear how a large customer extended its process model, supports its enterprise scale Scrum projects and Acceptance Driven Development. Additionally, learn how the template takes advantage of the new hierarchical work item capabilities, integrates with Microsoft Test and Lab Manager and supports the new deployment topologies for TFS 2010.
These two videos show how to use the refactoring tools in Visual Studio.
In this episode of 10-4 we look at a new type of test coming in Visual Studio Team System 2010 known as the coded UI test. Coded UI tests can be created to automatically navigate through your application’s UI, which in turn can be used to verify that the paths your users might take through your application are working properly. You can also add validation logic along the way to verify the properties of objects within the UI. Much like unit tests can quickly surface regressions on a method or function level, coded UI tests can bring the same level of rapid automated testing capabilities to the UI layer.This demo is based on an early build of Visual Studio Team System 2010 Beta 1.
Nikolai Tillmann and Peli de Halleux give a short tutorial on Pex, an automated white box testing tool for .Net. The tutorial is a pair-programming session where they show us how to get started with Pex in Visual Studio, starting from an (untested) piece of C# code:
* how to use Pex to explore the behavior of any method in your code,
* how to save the exploration results into a unit test suite,
* how to improve the generated parameterized unit tests to leverage Pex code exploration engine.
If you want to follow up the steps on your machine as well,
* Download Pex from DevLabs
* Download the code example
* Ask your questions in the forum
Pex is a white-box test generation tool for .NET. Starting from a hand-written parameterized unit test, Pex analyzes the program-under-test to determine relevant test inputs fully automatically. To this end, Pex executes the program multiple times with different inputs while monitoring the taken execution paths. Pex uses a constraint solver to determine new test inputs that will exercise different execution paths. As a side effect, Pex may find errors in the program. The result is a traditional unit test suite with high code coverage. In addition, Pex suggests to the programmer how to fix certain errors. Pex is integrated into Microsoft Visual Studio.
In this screencast we will demonstrate how to use the Object Builder pattern to create and setup objects for tests. In the first part we discussed how to introduce the base class for the unit tests to improve readability and cleanness of code.
In this screencast we will refactor unit tests to make it more readable. It is very important that you refactor your unit tests. Unit test code is not part of the production but refactoring them can help you in the long run and will provide benefits when maintaining the application.