נתחיל בלומר שה – Test Scribe הוא כלי חינמי אותו ניתן להוריד מהלינק הבא:
ה – Test Scribe יכול לייצר לנו מסמכים מיתוך Test Plan ומיתוך תוצאות הרצה.
בפוסט הזה אני יראה איך יוצרים מסמך Software Test Description ומסמך Software Test Results
איך יוצרים STD?
צעד 1: הפעל את ה - MTM
צעד 2: לאחר התקנת ה – Test Scribe יופיע טאב נוסף הניקרא Tools עבור לטאב זה.
צעד 3: בחר “Test Plan Summary”
צעד 4: בחר תוכנית בדיקות, בדוגמא זו בחרתי את תוכנית הבדיקות שניקראת “Iteration 2”
צעד 5: לחץ על Generate
ה – Test Scribe בשלב זה ייצור את המסמך
התוצאה: מסמך STD מבוסס תוכנית בדיקות.
I get this question a lot!!!
How do I reuse my Test Suites?
In MTM we have a very easy way of reusing Test Suites, just follow these steps:
Here I have created a source plan with Test Suite to copy, the Test Suite contains Requirements and Test Cases.
Step 1: Create a new Test Plan
Step 2: From the Plan tab click the small arrow button that will launch the “Copy Test Suites From Another Test Plan” window
Step 3: Choose the Test Plan from the dropdown list
Step 4: Choose the Test Suite to copy
Step 5: Click the “Copy suite into plan” button
on May 31st I will start the course on MTM and Test automation in Ness Collage.
The course is 40 academic hours, one session a week in the evening.
In this course I will show how to use Microsoft Toolbox for Manual and Automation Testing.
For more information and registration:
I hope too see you there…
The Video Recorder uses the Expression Recorder 4 to record the video from the screen.
The result is a link that ends with .xesc that you will not be able to play.
What can we do in order to play it?
In order to play these files install one of the two:
Expression Encoder 4
Screen Capture Code
After installing One of the two Windows Media Player will be able to play these files.
Note: The second one is the codec only and is included in the first
It was great!!!
My first session was about the “Visual Studio Testing Tools” for better quality and my second session was about BI in the Service of the Tester.
you can see my previus post regarding this event: "My Session in “Next Generation Testing with Microsoft Visual Studio 2010” Tomorrow"
You can download my Power Point Presentation from here.
You can also watch the videos in this link: http://blogs.microsoft.co.il/blogs/msdn/archive/2011/02/17/next-generation-testing-14-02-2011.aspx
Many thanks for all the people that made it happen and helped me in my preparations!!!
Tomorrow is a big day for me!
I am about to give a session about testing with the Microsoft Testing Tools that were released with the Visual Studio 2010 and TFS 2010.
Unfortunately the registration was closed a few days ago due to lake of sits.
I apologize I know that many people couldn’t get a sit on time, some have personally called me but there is nothing I can do about it, we have saved the biggest room Microsoft has to offer.
I will try to save another date for this event, I promise to publish the new date if there will...
There are times where we need to do a Visual Verification to our application, in Coded UI tests this task is now possible using the TestApi.
“TestApi is a library of test and utility APIs that enables developers and testers to create testing tools and automated tests for .NET and Win32 applications. TestApi provides a set of common test building blocks -- types, data-structures and algorithms -- in a simple, layered, componentized and documented stack.”
The TestApi can be downloaded here.
A good explanation of how to add the Visual Verification to the Coded UI Test can be found in Ivo Manolov’s...
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.
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...
Many times when I go to a client and tell him that his QA team needs to start at the beginning of the project's development process I see a wondering look at his eyes.
A good QA process needs to start as early as possible in the development process, the type of testing that is being done at that early stage called "Static Testing".
"Static Testing" is basically documentation testing and code testing but without using the software, for example "Code Reviews".
When the software is used for testing it is called "Dynamic Testing".
In this post I will focus on the...
Finally it is here!
I have writen about the feature pack 2 in my post: “New Feature Pack For Testing Is About To Be Delivered Including Silverlight Support!”
You can download the feature pack only if you are a MSDN Subscriber and you have Visual Studio 2010 Ultimate Edition Premium Edition or Test Professional from here.
The Feature Pack 2 is already including Feature Pack 1.