Eran Ruso : tfs guides

איך יוצרים מעבדה סטנדרטית\פיזית (Standard\Physical)

Eran Ruso — Wed, 29 May 2013 06:02:00 GMT

הפוסט שכתבתי בנושא זה פורסם ב – MSDN Blog, ניתן לקרוא אותו כאן

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

תיהנו!!!

==============================================================================================================

בגרסת ה – TFS 2010 הציגו לנו מיקרוסופט כלי חדש שניקרא: Microsoft Test and Lab Management או בקיצור MTLM.

לאחר זמן קצר הוחלט לקרוא לו MTM, הוא מוכר גם כ – Test Professional.

הרוב מכירים את יכולת הבדיקות של הכלי, לרוב משתמשים בו הבודקים.

מעטים מכירים את יכולות ה – Lab של הכלי.

ישנם שתי יכולות עיקריות של Lab:

1) מעבדות פיזיות או כפי שהן מכונות ב – TFS 2012 מעבדות סטנדרטיות – מעבדות אילו מבוססות על מחשבים פיזיים, זה גם כולל מחשבים וירטואליים על VMWare.

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

2) מעבדות וירטואליות – מעבדות אילו מבוססות Hyper-V ונשלטות על ידי ה – SCVMM שמחובר ל – TFS, החיסרון בשיטה זו הוא הצורך בחומרה חזקה, היתרון מגיע ביכולות ה – Snapshot ברמת המעבדה. לדוגמא אני רוצה להכין מעבדה, “להקפיא” אותה ולאחר מכן להריץ בדיקות שילכלכו אותה, בסיום הבדיקה כול מה שאני צריך לעשות זה Revert למצב “המוקפא” ואני מוכן להרצת בדיקות מחדש ו\או נוספות.

בפוסט הזה אני יראה איך אני מייצר מעבדה סטנדרטית\פיזית, נשתמש בסוג מעבדה זו בעיקר להרצות של בדיקות אוטומטיות.

יש להתקין את ה – Test Controller כדי לבנות מעבדה פיזית ניתן להוריד אותו מהלינק הבא:

http://www.microsoft.com/en-us/download/details.aspx?id=30655

הערה: יש להתקין את ה – Test Controller בלבד

על מנת לייצר מעבדה סטנדרטית\פיזית יש לבצע את הצעדים הבאים:

צעד 1: לאחר התקנת ה – Test Controller יש לבצע קינפוג, נריץ את ה- Test Controller Configuration

צעד 2: נזין שם משתמש וסיסמה, משתמש זה יריץ את ה – Service של ה – Test Controller (חץ כחול)

צעד 3: נחבר את ה – Test Controller ל – Collection ב – TFS בו נשתמש (חצים אדומים)

צעד 4: נגדיר משתמש שיריץ את ה – Lab service במקרה הזה השתמשתי באותו שם משתמש (חצים ירוקים)

צעד 5: נלחץ על Apply Settings לסיום הקינפוג

צעד 6: לאחר סיום הקינפוג יש ללחוץ Close

צעד 7: נפעיל את ה - MTM

צעד 8: נעבור ל – Lab Management, יש לשים לב שאנחנו עובדים על ה – Collection הנכון

צעד 9: נוודא שיש לנו Test Controller תקין, נעבור לטאב Controllers ונבדוק שה – Test Controller לא מסומן ב – X אדום

צעד 10: נעבור לטאב Lab ונלחץ על New ליצירת מעבדה חדשה

צעד 11: נבחר Standard environment, נזין שם למעבדה ונעבור לטאב Machines

צעד 12: נלחץ על Add machine להוספת מחשבים חדשים

צעד 13: נזין את שם המחשב ונבחר לו Role מהרשימה, כמו כן נזין לו שם משתמש שיש לו הרשאות על המחשב

שים לב: תהליך זה יתקין ויקנפג Test Agent על מחשב זה, במידה ויש כבר Test Agent המחובר ל – Test Controller ניתן לבחור מרשימה קיימת של מחשבים, לינק אל הרשימה תופיע בתחתית החלון.

צעד 14: נעבור ל – Advanced ונסמן את Configure environment to run UI tests

צעד 15: נבחר על איזה מחשב ירוצו בדיקות ה – GUI, נזין שם משתמש וסיסמה בעלי הרשאות ונעבור לטאב Verification

צעד 16: נלחץ על Verify ונוודא שהכול ירוק

צעד 17: כעת המערכת מתקינה ומקנפגת את ה – Test Agent על המחשב שהזנו קודם

שימו לב שבמהלך ההתקנה המערכת תבצע Restart לבד וגם תבצע Log-in לבד.

זה הכול יש לכם מעבדה עובדת…

תיהנו!!!

איך מזינים את השעות האפקטיביות של כול איש פיתוח במערכת ה–TFS?

Eran Ruso — Thu, 10 Jan 2013 14:16:00 GMT

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

לכולנו יש זמן לא אפקטיבי במהלך היום, הזמן בו אנחנו מכינים קפה/תא, הזמן בו אנחנו אוכלים, ישיבות בהם אנחנו משתתפים וכו’.

ב – SCRUM אנחנו מגדירים זמן אפקטיבי עבור צוות SCRUM, ב – TFS 2012 ניתן להגדיר שעות עבודה עבור כול עובד כאשר ניתן להגדיר 9 שעות אך המלצתי היא להגדיר שעות אפקטיביות אז ניתן להיות הרבה יותר מדויקים בניהול הפרויקט, כמובן שיש לזכור גם לתזמן את המשימות בשעות אפקטיביות.

אז איך עושים את זה?

הערה: ניתן לעשות את זה רק ב – TFS 2012 בעזרת ה – Web Access.

צעד 1: יש להריץ את ה – Web Access

צעד 2: לחץ View backlog

צעד 3: בחר Iteration/Sprint תלוי בשמות שנתתם ל – Iterations

צעד 4: לחץ Capacity

צעד 5: הזן שעות עבור כול עובד, ניתן גם לקבוע את התפקיד של כול עובד באטרציה הזאת (Activity)

צעד 6: לחץ על סימן ה – + בשורת העובד כדי לקבוע תאריכי חופשה עבור העובד האיטרציה הנבחרת

צעד 7: ניתן לקבוע באותו האופן ימי חופשה עבור כול הצוות, חופשות לדוגמא

ובזה סיימנו…

תיהנו!!!

Visual Studio Test Manager 2010 – Exploratory Testing

Eran Ruso — Tue, 07 Dec 2010 13:58:00 GMT

One of the things missing in most of the Testing Tools is the “Exploratory Testing”, where the tester runs an unmanaged tests which means that no steps reproduction is done when he finds a bug.

Not Anymore…

In Visual Studio Test Manager 2010 there is a great function called Exploratory Bug, so how do we use it?

Step 1: First create a Test Case that will be the shell for the exploratory test, all you will need to do is write the Title and the meta data for the Test Case

Step 2: Run the test case from the “Test Tab”

Step 3: Check the “Create Action Recording” checkbox

Step 4: Click the “Start Test”

You can see the “Currently Recording” icon on the recorded window

Step 5: Explore your application up to the point where you find a bug

Step 6: From the toolbar open the “Bugs Dropdown List” and choose: “Create exploratory bug”

At this point you will have a bar that shows you the test time range where the collectors have collected your test data.

If your test was long you will not need to save all the collected data in order for the developer to reproduce the bug, part of this data will be more than enough.

Step 7: Choose the range of data from the collectors you like to save to the bug.

Step 8: Click “Use range to create bug”

The Test Manager will automatically open as new bug with all the collectors data you have chosen to save.

You can see this data in the following Screenshots:

Screenshot 1: The bug and its data in the “Details Tab”

Screenshot 2: User Action Log

Screenshot 3: Event Log

Screenshot 4: Video

Screenshot 5: System Information

There is more information that you can collect in your test, the information that will be collected is depend on the collectors that you “turn on” in your test settings.

Have Fun!!!

TFS 2010 Alerts User Guide – How To Set The Mail Server

Eran Ruso — Tue, 12 Oct 2010 12:06:00 GMT

This post is the Second post out of Five that builds the TFS 2010 Alerts User Guide. See the first post: “TFS 2010 Alerts User Guide – Introduction”

On this post I will show how to set the mail server.

The first thing you will need to do in order to user the Alerts mechanism is to set an SMTP server that the TFS will use.

Follow these steps to set the SMTP:

Step 1: Log in to the Server with a user that has TFS Administration rights

Step 2: Launch the “Team Foundation Administration Console”

Step 3: Go to the “Application Tier”

Step 4: Click the “Alert Settings”

Step 5: Type your SMTP Server

Step 6: Type an Email address, you can type a fake email address it doesn’t need to be a real one. I usually use: TFSAdmin@DomainName.com

The result will be:

That is all, you are now ready to start using the Email Alerts.

Have Fun!!!

TFS 2010 Alerts User Guide – Introduction

Eran Ruso — Sun, 26 Sep 2010 16:57:00 GMT

Many times I am being asked about the Email alerts in TFS, I must admit that I had been lazy lately regarding this subject but that is now changed with this new User Guide.

There are two alert methods to be used:

Pull Alerts – Where the user decides which alerts to receive
Push Alerts – Where the administrator decides which alerts each of the users will receive

The Pull Alerts in my opinion is an unnecessary using Team System and I will explain why:

In Team System you get all the information where ever you are and what ever tool you are using, if you are using Visual Studio you have the Team Explorer in it, if you are using the Test Manager you have all the information in it too, you can get the information thru Excel, thru MSProject, Word, SharePoint, Web Access you can even create your own clients so why do I need someone that will push me unnecessary emails?

For organizations that decide to use the Push Method it can be done using Web Services that gets events from the TFS and send emails to who ever the Administrator decides, this subject is out of the scope of this User Guide I like to focus on the Pull Alerts Method.

What you will see in this User Guide?

How To Set The Mail Server
How To Define Emails For Work Items
How To Define Emails For Builds
How To Define Emails For Source Control Items

See you in the next post…

Have Fun!!!

TFS 2010 Coded UI Test Basic User Guide Is Published

Eran Ruso — Tue, 29 Jun 2010 14:16:00 GMT

I am glad to announce that the TFS 2010 Coded UI Test Basic User Guide Is finally done and available to download.

I have worked hard to create this guide and I will be glad to hear what you think of it.

It is available to download from the TFS Guides site.

I will also like to know what other user guides you need.

Have Fun!!!

Visual Studio 2010 Coded UI Test User Guide - Add Validation To Your Coded UI Tests

Eran Ruso — Mon, 17 May 2010 03:50:00 GMT

This post is the Fourth post out of Four that builds the Visual Studio 2010 Coded UI Test User Guide. See the first post: “Visual Studio 2010 Coded UI Test User Guide - Introduction”, the second post: “Visual Studio 2010 Coded UI Test User Guide - Create A Simple Coded UI Test” and the third post: “Visual Studio 2010 Coded UI Test User Guide - Get A Coded UI Test Created In Manual Test Using The MTM Tool”

On this post I will show how to add validation rules to the Coded UI Test that we have previously recorded.

This post is based on the example made in the second post of this guide: “Visual Studio 2010 Coded UI Test User Guide - Create A Simple Coded UI Test”

Now that we have the code for the Coded UI Test we can add validation rules.

The validation rule I like to add will be placed after the last method of the test “this.UIMap.UpdateYourShoppingCart()” and I will call it: “CheckSubtotal”

Follow these steps to add this validation:

Step 1: Place the mouse cursor after the last method this.UIMap.UpdateYourShoppingCart() in the test.

Step 2: Right click choose “Generate Code for Coded UI Test” –> “Use Coded UI Test Builder…”

The Coded UI Test Recorder launched

Step 3: Drag the cursor to the object you like to validate, in this case the “Subtotal”

The ID of the object is shown

Step 4: Choose the property to validate and click: “Add Assertion”

A new window pops up with the assertions available.

Step 5: Choose the Comparator and the Comparison Value

Step 6: Click OK

You will see a mark next to the property indicate that a validation rule was added

Step 7: Click the “Generate Code” button

Step 8: Type the name of the method and click “Add and Generate” button

You can see that the method was added to the “TestMethod” and will run with the test.

You can see that it is easy to add validations to the test, use validations as much as you can.

I have also published a video that shows all the steps and examples from this guide: "Coded UI Test Demo – Video Hebrew"

Have Fun!!!

Visual Studio 2010 Coded UI Test User Guide - Get A Coded UI Test Created In Manual Test Using The MTM Tool

Eran Ruso — Tue, 20 Apr 2010 04:13:00 GMT

This post is the Third post out of Four that builds the Visual Studio 2010 Coded UI Test User Guide. See the first post: “Visual Studio 2010 Coded UI Test User Guide - Introduction” and the second post: “Visual Studio 2010 Coded UI Test User Guide - Create A Simple Coded UI Test”

On this post I will show how to create a Coded UI Test based on prerecorded Coded UI Test.

In the Microsoft Test Management (MTM) tool you run Test Plans with the Test Runner, In case that the “Action Log and Action Recording” collector is turned on the Test Runner will create a Coded UI Test in the background while running the Manual Test.

The recorded Coded UI Test is very simple and basic test that will not answer the Automation Test Effort requirements but its a start.

The Tester that is assigned on creating the Automated Tests can have a very good starting point using these prerecorded tests.

The way to do it is based on one of the posts I have already published that covers this section: “Creating A Coded UI Test From A Manual Recording In TFS 2010”

Next Guide Part: "Visual Studio 2010 Coded UI Test User Guide - Add Validation To Your Coded UI Tests"

Have Fun!!!

Visual Studio 2010 Coded UI Test User Guide - Create A Simple Coded UI Test

Eran Ruso — Sun, 28 Mar 2010 00:47:00 GMT

This post is the Second post out of Four that builds the Visual Studio 2010 Coded UI Test User Guide. See the first post: “Visual Studio 2010 Coded UI Test User Guide - Introduction”

On this post I will show how to create a simple Coded UI Test.

The example I will use in this guide created by Microsoft and is called: “IBuySpay”

The example is a web application but we will use its GUI in the Coded UI Test.

A few guide lines before we start:

To create a test you need to have a Test Project
Base every Automated Test on a predefined Test Case
Every step in the Test Case will be a Method in the Coded UI Test

Note: In this example I will not show the Test Case.

Creating a Test Project

Step 1: Right click the Solution choose: Add –> New Project…

Step 2: Choose Test from the Menu, in my example it will be a C# Test Project

Step 3: Choose the location and the name of the test project and choose Create

The result is the test project (DemoIBuySpyTest) and 3 more solution items that are added in case this is the first test project.

These 3 files are out of the scope of this guide.

Creating a Coded UI Test

Step 1: Right click the Test Project choose Add –> New Test…

Step 2: Choose Coded UI Test

Step 3: Type a Test name and click OK

Step 4: In the window that pops up choose the first option: “Record actions, edit UI map or add assertions”

Step 5: Click OK

The Recorder launches.

The Recorder has 4 buttons (From left to right):

Record – Will record actions
Show Recorder Steps – Shows what was recorder and lets the user edit the steps
Add Assertion – Lets the user choose objects and to get there “Passport”, it also lets the user add validation to objects
Generate Code – Lets the user create code out of the recorder actions

Step 6: launch the Internet Explorer Browser

Step 7: Click Record

The icon will be changed to Pause

Step 8: Type the URL of the tested site

Following the guide lines we need to create a method for each step in the Test Case

Step 9: Click the Pause button

Step 10: Click the “Show Recorder Steps” in order to see and edit the recorder steps

You can see that there is only one recorded steps, in order to edit the recorded steps (If needed) choose the step and click the Delete button in your keyboard.

Step 11: Click the “Generate Code”

Step 12: Type the name of the method

Step 13: Click the “Add and Generate” button

The result is the code generated in the “DemoCodedUITest.cs” TestMethod and new files created, these files have the UI objects mapping.

You can also see the Method we have created.

I have created a few more methods that represent a few more steps.

In order to run the test you can right click the Coded UI Test name and choose “Run Tests”.

We have created a simple Coded UI Test, next on this guide we will see we will see how to reuse a prerecorded Coded UI Test in the MTLM tool.

Next Guide Part: "Visual Studio 2010 Coded UI Test User Guide - Get A Coded UI Test Created In Manual Test Using The MTM Tool"

Have Fun!!!

Visual Studio 2010 Coded UI Test User Guide - Introduction

Eran Ruso — Thu, 25 Feb 2010 13:33:00 GMT

In Visual Studio 2010 Microsoft has added the Coded UI Test.

Back to history:

In Visual Studio 2005 Microsoft presented the Tester Edition, it contained the following parts:

Web Test Automation Test
Performance Test
Unit Test
Something that should have been a Manual Test, it was word or text documents contained the Test Cases. Practically no one used it.

In Visual Studio 2008 tester edition no significant changes has been made.

In Visual Studio 2010 Microsoft added more parts to the Tester Edition and created a new tool for the Tester called Microsoft Test and Lab Management (MTLM).

I will not get into all the new functionality added to Team System 2010 but I will list the main parts:

Web
Web Test Automation Test
Performance Test
Unit Test
Test Cases management
Manual tests
Coded UI Tests
Lab Management

In the following 3 posts of the user guide I will focus on the main tasks using the Coded UI Test, best practices with the tool and with automation tests in general.

These are the Blog Posts subjects:

The Guide will be published in my codeplex project: “TFS Guides” when finished, you can also find there more TFS guides.

I have also published a video, the video shows all the steps and examples from this guide: “Coded UI Test Demo – Video Hebrew”

Have Fun!!!

Delete TFS 2010 Work Items

Eran Ruso — Thu, 18 Feb 2010 18:47:00 GMT

Many customers ask me about deleting Work Items from the TFS.

Here is how to do it for TFS 2010:

Step 1: Log-in to the TFS using a TFS administrator user.

Step 2: Open a command line and go to:

32bit machine - “X:\Program Files\Microsoft Visual Studio 10.0\Common 7\IDE”
64bit machine - “X:\Program Files (x86)\Microsoft Visual Studio 10.0\Common 7\IDE”

Step 3: Use the “witadmin.exe destroywi” command in the following way:

witadmin.exe destroywi /Collection:http:\\[ServerName]:8080\tfs\[CollectionName] /id:[WI ID]

you can add as many Work Item IDs as you like using [,] for example 54,88,92 etc.

You can disable the prompt message by using /noprompt.

For deleting work items in TFS 2008 see:
http://blogs.microsoft.co.il/blogs/eranruso/archive/2009/08/10/delete-tfs-work-items.aspx

Have Fun!!!

TFS 2010 Work Items Basic User Guide Is Published

Eran Ruso — Mon, 01 Feb 2010 13:00:00 GMT

I am glad to announce that the TFS 2010 Work Items Basic User Guide Is finally and available to download.

I have worked hard to create this guide and I will be glad to hear what you think of it.

It is available to download from the TFS Guides site.

I will also like to know what other user guides you need.

Have Fun!!!

How To Configure Build Services To A Specific TFS 2010 Collection

Eran Ruso — Mon, 25 Jan 2010 16:04:00 GMT

In TFS 2010 we use collections, collections act as different “Servers” that the team can use in order to create separation between different groups of projects.

The build services can service one collection at a time.

In order to change the collection that the Build Services is servicing do the following:

Step 1: Launch the “Team Foundation Administration Console”

Step 2: Choose the “Team Foundation Build Configuration” menu item

You can see the collection that is being served at point 1.

Step 3: Stop the build service. (Point 2)

Sep 4: Click on the build “Properties” option

Step 5: In the properties window click the “Browse…” button.

Step 6: To choose the target collection mark it and click the “Connect” button

Step 7: Now that you have all in place start the build service.

Note: Some times it will fail to restart, just retype the Password of the account that runs the build service and try again.

At this point you will have the build service up and running, if it is the first time you specify the build services to service this collection you will need top create a controller and an agent.

Step 8: Click the “New Controller”.

Step 9: Choose a name for the controller and click “OK”.

Step 10: Wait until the controller will be ready and add a new Agent

Step 11: Choose a name for the Agent, you can also add tags and set the working folder for the agent, when done click “OK”

Step 12: See that all are in read state in order to start creating builds, you can also add more agents for this controller.

Now all is done you can go to the collection’s projects and use the build services.

Have Fun!!!

TFS 2010 Work Items Basic User Guide – Create New Work Items Out Of An Existing Work Items

Eran Ruso — Mon, 11 Jan 2010 14:00:00 GMT

This post is the Fifth post out of Five that builds the TFS 2010 Work Items Basic Guide. See the first post: “TFS 2010 Work Items Basic User Guide – Introduction”

I have already published regarding the creation of new Work Items: “TFS 2010 Work Items Basic User Guide – Create New Work Items”, about the Work Item Links: “TFS 2010 Work Items Basic User Guide – Work Item Link Types” and about creating and using queries: “TFS 2010 Work Items Basic User Guide – Create And Use Queries”

On this post I will talk about creating Work Items out of existing work items.

Creating Work Items out of existing Work Items can be done in two ways:

Create a copy of the existing Work Item
Create a related Work Item to the Existing Work Item

To create a copy do the following:

Step 1: Open the existing Work Item and Click on the “Copy Work Item” button.

In the screenshot you can see the existing Work Item.

Step 2: Choose the target Team Project and the Work Item Type.

You can choose any Work Item Type you like, I have chosen the same type “Requirement”.

What you will now have is a copy of the source Work Item, in case you will choose to create a different Work Item Type from the source Work Item Type only the sheared fields will be filled.

In the Links tab of the new Work Item you will see a link to the source Work Item.

When saving your new Work Item you will get cross links, there will be a link from the source Work Item to the new Work Item and vice versa.

Many times you will need to create Work Items that are similar, using the copy Work Item option saves a lot of Copy/Pastes and time.

To create a related Work Item do the following:

Step 1: Open the existing Work Item and Click on the “New Linked Work Item…” button.

Step 2: Choose the type of the link the Work Item Type type the Work Item title and click the OK button.

A new work item is now created that will be linked to the Existing Work Item, the link type is the one you have chosen in step 2.

All you got left to do is “Save” the new Work Item.

That was the last post in the “TFS 2010 Work Items Basic User Guide”, it is not an easy work writing it so I will really appreciate your comments (Good or Bad) on it.

Have Fun!!!