I have started to write about the “Microsoft Test And Lab Management” in the Introduction post where I presented three sections in the tool: Testing Center, Lab Center and Organize.

You can read the post “Team System 2010 Beta 1 “Microsoft Test And Lab Management” - Introduction” of the introduction.

I intend to create a quick guide for the “Microsoft Test And Lab Management” out of these posts that will be published in the “Team System Guides”.

When working with the “Microsoft Test And Lab Management” for the first time you will need to start with the Organize section where you do 4 things:

1. Create Sheared Steps for Test Cases
2. Create Test Cases
3. Create Configurations
4. Create Test Plans

You can start by doing each of the tasks, the order here is the order I will use for my example.

I have already published how to manage shared steps “Microsoft Test And Lab Management – Create And Manage Shared Steps (Part 1)”.

In this post I will show the Test Cases.

Step 1: In order to open the “Organize” launch the tool and select the Organize option.

The “Organize” toolbar will be shown.

Step 2: Click on the “Test Cases” option to get to the Shared Steps management.

Step 3: Clicking on the “New” button will open a new Test Case form.

The first part of the form is for managing the item.

Second part of the form is the Steps, Summary, History, Links and File Attachments.

I like to focus on the Steps section, all the other parts are similar to regular work items.

In the Steps tab you can see two parts:

1. Steps, Expected Results and the step attachment.
2. Parameters

In the steps I will use the @ to refer to a parameter.

In the parameters section I have entered two lines, each line of parameters will be an iteration of the test when I run it later in the process.

After filling all the fields all you left to do is click on the “Save and Close” button or the “Save” button and you will have a Test Case ready to run.

There is one more function I haven’t talked about in the “Test Cases Manager”, the Create Copy Button – Highlighting a Test Case line and click the button will create a new Test Case item with the steps already written, saves time when there are similar scenarios with small changes.

You can always modify the Test Case Steps, just open the item, make all the required changes and save it again.

Have Fun!!!

• קרא עוד
• 4 תגובות

בישראל בשנת 1998 הוספה תקנה לפקודת בריאות העם המחייבת הפלרת מי שתייה בכל ישוב שבו מתגוררים לפחות 5000 תושבים.

פגשתי את אייל גיא מרום ואת טל טואשי באוהל מחאה בגן הורדים שליד משכן הכנסת הם שיכנעו אותי לבדוק מה זה אומר.

אני משאיר לקורא להחליט האם זה טוב או רע.

כמו תמיד אני ממליץ לבדוק את שני הצדדים בנושא לפני שמגיעים להחלטה.

מה אתה חושב?

• קרא עוד
• 3 תגובות

I have started to write about the “Microsoft Test And Lab Management” in the Introduction post where I presented three sections in the tool: Testing Center, Lab Center and Organize.

You can read the post here.

This is the first part out of four for the Organize section, later I will post about the Testing Center section but I still don’t know how many parts I will posts for that section.

I intend to create a quick guide for the “Microsoft Test And Lab Management” out of these posts that will be published in the “Team System Guides” that can be found here.

When working with the “Microsoft Test And Lab Management” for the first time you will need to start with the Organize section where you do 4 things:

1. Create Shared Steps for Test Cases
2. Create Test Cases
3. Create Configurations
4. Create Test Plans

You can start by doing each of the tasks, the order here is the order I will use for my example.

In this post I will show the Shared Steps and on the following three posts I will show the Test Cases, Configurations and the Test Plans.

Step 1: In order to open the “Organize” launch the tool and select the Organize option.

The “Organize” toolbar will be shown.

Step 2: Click on the “Shared Steps” option to get to the Shared Steps management.

Step 3: Clicking the “New” button will open a new Shared Step form.

The first part of the form is for managing the item.

Second part of the form is the Steps, Summary, History, Links and File Attachments.

I like to focus on the Steps section, all the other parts are similar to regular work items.

In the Steps tab you can see two parts:

1. Steps, Expected Results and the step attachment.
2. Parameters

In the steps I will use the @ to refer to a parameter, the parameter is changing from one test to another and I will show it when we get to create the Test Case.

After filling all the fields all you left to do is click on the “Save and Close” button or the “Save” button and you will have a shared test steps ready to be used in Test Cases.

There are two more functions I haven’t talked about in the “Shared Steps Manager”:

1. Create Copy Button – Highlighting a shared steps line and click the button will create a new shared steps item with the steps already written, saves time when there are similar scenarios with small changes.
2. Create action recording button – Highlighting a Shared Steps line and clicking on this button will launch the Test Runner allows you to create a recording for the steps. This is a very powerful function and I will talk about it in future posts.

You can always modify the Shared Test Steps, just open the item, make all the required changes and save it again. All the Test Cases will be automatically updated with the change.

Have Fun!!!

• קרא עוד
• 10 תגובות

• קרא עוד
• אין תגובות

Usually I write about Team System or about Methodologies, today I make an exception…

I have made a small research about the new office, Office 2010 and it is really cool!

Microsoft is giving a fight to Google Docs and they are doing a good job.

The new office will be available thru the usual way we all know using the desktop, in addition to that you will be also able to get to your files thru the web and using your mobile computer.

You can see the applications that will be apart of the Office 2010 in the following great movie:

Have Fun!!!

• קרא עוד
• אין תגובות

I have recently announced the Team System 2010 overview lecture that will take place in the following ALM group in Microsoft, you can read more about it here.

I am about to talk about the “Testing” part of the lecture, were I will show the new tool for the testers – “Microsoft Test and Lab Manager”.

I hope you will enjoy it…

Have Fun!!!

• קרא עוד
• אין תגובות

YES WE DO!!!

Not once I hear that when using Agile Development Methodologies you don’t need testers, “We are using Test Driven Development (TDD) that covers everything so why do we need testers for?”

It is true that when using the Test Driven Development (TDD) or regular unit tests the quality of the software is much better but it is definitely not instead of testers, unit testing is for testing units what about integration testing, system testing, black box, white box etc. all are not covered by unit tests.

Lets look at an example:

Log-in

scenario: A log in scenario needs to have a user name and a password.

TDD or Unit Tests: Will check that when I pass credentials (User name and password) to a method that authenticate the credentials it will return true when the credentials are “good” and false when the credentials are incorrect.

Tester: Will test the input formatting in each of the fields, will check the boundaries of the fields, will check what appends when the log-in failed, will check what appends when the log-in success, will check the usability of the log-in screen, will check if a certain log-in credentials gives the right permissions in the application etc.

You see that the unit tests and the tester have a different scopes for what they test, the lists are incomplete and depends on the application under test but I hope I made it clear that the tester rule can’t be skipped no matter what methodology is being used.

The rule of the tester is changing when using Agile Development Methodologies, a change that requires a different approach.

In None Agile Development Methodologies the specification of the software is written before the code, the testers gets all the specifications, write the test plan and all the test cases, only than the tester receives the build and start to test.

In Agile Development Methodologies the specification of the software is written during the coding what makes the life of the tester a little different, the tester needs to react to changing requirements that evolves during the development.

In Agile Development Methodologies the tester is part of the development group and the time he have to test is the sprint/Iteration time, the tests that are done by the tester are most of the time relate to the part that is being developed in the sprint/Iteration.

What about Tests that relates to the complete product?

Depends on the project, the most likely situation is a tester in the development group tests the developed part of the system and later in the development process before the release to the customer there is a group of testers that does all the integration tests, system tests, performance tests etc.

Have Fun!!!

• קרא עוד
• 1 תגובות

With the Team System 2010 Beta 1 the Manual Testers have received a great tool called “Microsoft Test And Lab Management”.

Every Microsoft tool has its code name and the “Microsoft Test And Lab Management is no different, the code name for this tool is “Camano”.

In this post I will give a brief overview of the tool, I will not show all the functionality of the tool in order to keep the post short and readable.

The tool is built of three main sections:

1. Testing Center – In this section the user can see the Test Plans, Run the Test Plan, Analyze the Test Results and manage the bugs.

2. Lab Center – Here the user can manage the different environments, machines both Physical and Virtual and Test Settings that defines the way the tests will run on each environment.

3. Organize – Here the user can manage its Test Cases, Shared Steps (Steps that can be sheared between different Test Cases), Configurations (Defines the content of the test environment, example: Win XP SP3 with IE 8.0) and finally the Test Plans that will be used in the “Testing Center”.

So where to start?

You need to start in the “Organize’ section where you plan your Test Cases, Configurations and Test Plans, you can choose the order.

How do I do that?

How to do it will be on my next “Camano” post…

Have Fun!!!

• קרא עוד
• 8 תגובות

In July 13 2009 16:30 – 20:15 we are about to present the main features and capabilities of the Team System 2010 Beta 1.

The lecture will take place at the Microsoft office in Rahanana and will be opened to everyone.

Registration to the event is required there are a limited places so hurry up and take a place, you can read more about the event and register here.

Have Fun!!!

• קרא עוד
• 2 תגובות

This morning when I worked with the Team Build 2010 Beta 1 I found a very nice surprise.

I work a lot with the Team Build and when I have a problem with the build I go to the log file, some of you that have encountered this “Monster” log file know that it is a “killer” for the eyeballs, it is a very long notepad file that lists all the steps made by the build engine and all the errors it has encountered.

You can see very short example of such a log at the end of this post.

So what is so exciting with the new Team Build?

The new Team Build presents the log file in a way that humans can read, the log has an hierarchy of actions and it hides the details so you can keep tracking of what happened during the build process.

What if you need the details? Just click on “Show Property Values” and you will have all the details shown in the hierarchy.

You can also navigate thru the log finding all the Errors and Warnings using the “Next Error” and “Next Warning” buttons.

Besides for the Team Build log there are many great surprises in the Team Build 2010, I will post more about it in future posts.

Have Fun!!!

Has promised here is the short log file example from the Team Build 2008, try to find something in it.
Tip: If you have troubles sleeping at night try to read one log file before bed time, It Works Like A Charm!!!

Build started 7/1/2009 9:32:53 AM.
Project "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\BuildType\TFSBuild.proj" on node 0 (EndToEndIteration target(s)).
Building with tools version "3.5".
Target "CheckSettingsForEndToEndIteration" in file "C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" from project "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\BuildType\TFSBuild.proj":
Task "Error" skipped, due to false condition; ( '$(BuildDefinition)'=='' ) was evaluated as ( 'test build'=='' ).
Task "Error" skipped, due to false condition; ( '$(BuildDefinitionId)'=='' ) was evaluated as ( '3'=='' ).
Task "Error" skipped, due to false condition; ( '$(BuildUri)'=='' ) was evaluated as ( 'vstfs:///Build/Build/30'=='' ).
Task "Error" skipped, due to false condition; ( '$(COMPUTERNAME)'=='' ) was evaluated as ( 'TFSRTM08'=='' ).
Task "Error" skipped, due to false condition; ( '$(TeamFoundationServerUrl)'=='' ) was evaluated as ( 'http://tfsrtm08:8080/'=='' ).
Task "Error" skipped, due to false condition; ( '$(TeamProject)'=='' ) was evaluated as ( 'TicTacToe'=='' ).
Using "Message" task from assembly "Microsoft.Build.Tasks.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Task "Message"
  BuildDefinition=test build
Done executing task "Message".
Task "Message"
  BuildDefinitionId=3
Done executing task "Message".
Task "Message"
  BuildUri=vstfs:///Build/Build/30
Done executing task "Message".
Task "Message"
  ComputerName=TFSRTM08
Done executing task "Message".
Task "Message"
  TeamFoundationServerUrl=http://tfsrtm08:8080/
Done executing task "Message".
Task "Message"
  TeamProject=TicTacToe
Done executing task "Message".
Done building target "CheckSettingsForEndToEndIteration" in project "TFSBuild.proj".
Target "InitializeBuildProperties" in file "C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" from project "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\BuildType\TFSBuild.proj":
Using "GetBuildProperties" task from assembly "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\Microsoft.TeamFoundation.Build.Tasks.dll".
Task "GetBuildProperties"
  GetBuildProperties TeamFoundationServerUrl="http://tfsrtm08:8080/" BuildUri="vstfs:///Build/Build/30"
Done executing task "GetBuildProperties".
Done building target "InitializeBuildProperties" in project "TFSBuild.proj".
Target "InitializeEndToEndIteration" in file "C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" from project "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\BuildType\TFSBuild.proj":
Using "UpdateBuildNumberDropLocation" task from assembly "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\Microsoft.TeamFoundation.Build.Tasks.dll".
Task "UpdateBuildNumberDropLocation"
  UpdateBuildNumberDropLocation TeamFoundationServerUrl="http://tfsrtm08:8080/" BuildUri="vstfs:///Build/Build/30" BuildNumber="test build_20090701.1" DropLocation="\\tfsrtm08\Drops\test build_20090701.1"
Done executing task "UpdateBuildNumberDropLocation".
Done building target "InitializeEndToEndIteration" in project "TFSBuild.proj".
Target "CoreInitializeWorkspace" in file "C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" from project "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\BuildType\TFSBuild.proj":
Using "DeleteWorkspaceTask" task from assembly "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\Microsoft.TeamFoundation.Build.Tasks.VersionControl.dll".
Task "DeleteWorkspaceTask"
  DeleteWorkspaceTask TeamFoundationServerUrl="http://tfsrtm08:8080/" BuildUri="vstfs:///Build/Build/30" Name="TFSRTM08_3" DeleteLocalItems=True
  TF14061: The workspace TFSRTM08_3;TFSRTM08\tfsBuild does not exist.
Done executing task "DeleteWorkspaceTask".
Task "DeleteWorkspaceTask" skipped, due to false condition; ( '$(SkipInitializeWorkspace)'!='true' and ('$(CleanCompilationOutputOnly)' == 'true' or '$(SkipClean)' == 'true') ) was evaluated as ( 'false'!='true' and ('false' == 'true' or 'false' == 'true') ).
Using "CreateWorkspaceTask" task from assembly "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\Microsoft.TeamFoundation.Build.Tasks.VersionControl.dll".
Task "CreateWorkspaceTask"
  CreateWorkspaceTask TeamFoundationServerUrl="http://tfsrtm08:8080/" BuildUri="vstfs:///Build/Build/30" Name="TFSRTM08_3" BuildDirectory="C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build" SourcesDirectory="C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources" Comment="Workspace created by Team Build"
Done executing task "CreateWorkspaceTask".
Done building target "CoreInitializeWorkspace" in project "TFSBuild.proj".
Target "CoreCleanAll" in file "C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" from project "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\BuildType\TFSBuild.proj":
Task "RemoveDir" skipped, due to false condition; (Exists('$(SolutionRoot)')) was evaluated as (Exists('C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources')).
Task "RemoveDir" skipped, due to false condition; (Exists('$(BinariesRoot)')) was evaluated as (Exists('C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Binaries')).
Task "RemoveDir" skipped, due to false condition; (Exists('$(TestResultsRoot)')) was evaluated as (Exists('C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\TestResults')).
Done building target "CoreCleanAll" in project "TFSBuild.proj".
Target "InitializeBuild" in file "C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" from project "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\BuildType\TFSBuild.proj":
Using "MakeDir" task from assembly "Microsoft.Build.Tasks.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Task "MakeDir"
  Creating directory "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources".
  Command:
  md "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources"
Done executing task "MakeDir".
Done building target "InitializeBuild" in project "TFSBuild.proj".
Target "CoreGet" in file "C:\Program Files\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets" from project "C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\BuildType\TFSBuild.proj":
Using "Get" task from assembly "C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\Microsoft.TeamFoundation.Build.Tasks.VersionControl.dll".
Task "Get"
  Get TeamFoundationServerUrl="http://tfsrtm08:8080/" BuildUri="vstfs:///Build/Build/30" Force=True Overwrite=False PopulateOutput=False Preview=False Recursive=True Version="C236" Workspace="TFSRTM08_3"
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources;C206.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\LocalTestRun.testrunconfig;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogic;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogicSolution.sln;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogicSolution.vsmdi;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogicSolution.vssscc;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogicTest;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogic\Board.cs;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogic\Cell.cs;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogic\Properties;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogic\TicTacToeDiagram.cd;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogic\TicTacToeLogic.csproj;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogic\TicTacToeLogic.csproj.vspscc;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogic\Properties\AssemblyInfo.cs;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogicTest\AuthoringTests.txt;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogicTest\BoardTest.cs;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogicTest\CellTest.cs;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogicTest\DataDrivenTesting.sdf;C207.
  Getting C:\Documents and Settings\TFSBUILD\Local Settings\Temp\TicTacToe\test build\Sources\TicTacToeLogicSolution\TicTacToeLogicTest\Properties;C207.

• קרא עוד
• 2 תגובות