Agile, Scrum webcasts to join has some create webcasts on subjects concerning Agile, Scrum. You can either sign up to them or go to the archive listing. Couple of interest are:

Agile Practices in a Traditional Organization

Adopting Test-First Development

Release Duration and Enterprise Agility

On May 15th is Agile and Quality: It is not an Oxymoron but a Necessity

Click here to check out the public webcast series.

Testa Smile

Microsoft MSDN Forum Gadget

If you are interested in following any of the MSDN Forum’s there is a gadget you can download that makes access to your favourite threads quick and simple.

Download here.

Testa [:)]

Create Reports for TFS2010 Test Results

Check out instructions on how to create reports for your TFS2010 Test Results. There is also an example that you can follow.

Testa Smile

Toronto VS ALM User Group kick off meeting April 12th

The first Toronto VS ALM User Group kick off meeting is being held on April 12th @6:30pm sign up at TALMUG to get the details and register.

The User Group is for all roles within the Application Life Management team. Topics presented will vary from generic ALM practices to ALM with Visual Studio. If your involved in product management, a stakeholder, a business analysis or product owner, a developer or a tester this User Group is for you.

The goal of the first meeting will be to:

  • Define the group’s mission
  • Select an appropriate name
  • Document the roles of the executive
  • Recruit volunteers
  • Funding
  • Discuss how to reach out for sponsors
  • Discuss meeting locations
  • Discuss ideas for the first few meeting topics

Come out on April 12th and help us to kick-off this new user group code named TALMUG.

Testa Smile

Functional/System testing with Visual Studio/Test Manager

If your reading this blog you likely understand what functional testing and you may use the term system testing.

Wikipedia defines these terms as:

System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic”

Functional testing is a type of black box testing that bases its test cases on the specifications of the software component under test. Functions are tested by feeding them input and examining the output, and internal program structure is rarely considered.”

If you have read Agile Software Engineering with Visual Studio (by Sam Guckenheimer & Neno Loje) you will have heard about “reducing waste”. Identified as tasks that reduce waste are functional and system testing. These two tasks can be done during code development through unit tests reducing the cost of bug fixes, bug analysis, creating a suite of automated tests and automated regressions tests and reducing the number of people involved in testing and the bug. In some teams developers and testers have been testing the same thing one through unit tests and then again later by a testers. This is duplication of work effort that is a expensive waste.

In Visual Studio there are unit testing tools and third party add in tools that developers can use to create very robust unit tests. You maybe thinking “the developers do not test the same “stuff” that testers do”. Your right, I agree. However since the team is encouraged to make changes to reduce waste why don’t we testers help them. In Visual Studio we can create test cases that are associated to the requirement/user story work item that describes what needs tested. We can pair up with developers to help them write robust unit tests to cover all the testing including boundary, error and data testing.

There are people that believe the future of the “software testers” is about to make a big change. Testers will need to be able to write and execute unit tests themselves therefore requiring the basics of coding and the ability to add assertions (validation) to the unit tests. (Check out MSDN’s Verifying Code by Using Unit Tests topics. ) I believe this will be a reality in the future but I also believe it will evolve.  If you want to start now pair up with your developers to help them create unit tests that execute both the “happy path” and boundaries of an individual method, class or component. Help them to create system integration tests. Getting expose to how unit tests are designed and coded will help you move into the future. In addition having knowledge of what has been unit tested reduces test duplication later. TFS and Visual Studio help us with all this through work item traceability.

Example of work item traceability:


Example of a Test Case and Associated Automation:


Visual Studio has the tools that will help us move into the future with confidence and the security we’ll need. Humans in general are not adapt to change but change we must. I am one of those people that embraces change and excels in change but then I have had Visual Studio in my pocket!

- Kent Beck

The role of professional testing will inevitably change from “adult supervision” to something more closely resembling an amplifier for the communication between those who generally have a feeling for what the system must do and those who will make it do.

Kent Beck author of Test-Driven Development (Addison Wesley 2002), 86.

Visual Studio – my companion, my mentor, my stability, my aid, my reporter, my success

Testa Smile 

(stay tuned, next blog  I will show you how easy it is to create a unit test!)

Microsoft Blogs – Canadian Solution Developer

If you are reading this blog you should check out bloggers, Susan Ibach and Jonathan Rozenblit. Microsoft developer evangelist who are the resident bloggers at Canadian Solution Developer. Susan and Jonathan are posting some very informative information on ALM, TFS, Visual Studio, testing, events coming, events happening now and in the past.

The most recent blog is about LinkedIn with some great tips on setting up a professional profile. What not to do and what is important to do. Click the link below to see what they have to say.

Microsoft Canadian Solution Developer blog

Testa Smile

Test Case customization by Dave Lloyd

The test case work item has a tab that lists the requirements/user stories that the test case tests. However, bugs related to the test case are not part of the listing. Dave has come up with a customization that changes the test case tab to include bugs created against the test case. With this customization you will see all work items that the test case tests.

Read Dave’s blog for more details and how to do the customization.

Testa Smile