Browse by Tags
All Tags »
Tests (
RSS)
I have posted about the “Microsoft Test and Lab Management” (MTLB) first when the Beta 1 was introduced. In this post I will show the changes made since Beta 1, you can read my post here . The menu in Beta 1 was this: In Beta 2 you can only find 2 sections: The Organize section is now part of the Testing Center sub menus. lets take a peek at the sub menus in the Beta 2: If you will compare that to Beta 1 you will see that the same functionality and menus stayed the same but is reorganized in the...
YES WE DO!!! You can read more on the blog post here . Have Fun!!!
I have seen many answers to this question, all talking about matrixes, what should I test, How should I test etc. Not many answers to this question talked about the overall process of development, the bigger picture… The testing process is part of much bigger picture of development that involves the developers, testers, managers, stockholders, marketing and more. Lets start with what stops the development in general, that will be the time to market of course, no product no matter how good it is will...
We have seen that our little bug was caught and documented on the last Bugs Life post, if you didn’t read that yet you can read it here . “ Dear diary, Today I have got my verdict, Obama the Project Manager has decided to “Fix” me. They say that it will be expansive to “fix” me but it will cost more to leave me unfixed, they say that this part of the software is not a critical part but still will be used by part of the customers and loosing there trust will cost more than the “fix” cost. Dennis the...
There are times when you need to write your own extraction rule, it is very simple to do that just follow these steps: Step 1: Create a new project, make it a “Class Library” type. Step 2: Add a reference to: Microsoft.VisualStudio.QualityTools.WebTestFramework.dll located in “Program Files\Microsoft Visual Studio 9.0\Common7\IDE\PublicAssemblies\”. Step 3: Add the following using: using Microsoft.VisualStudio.TestTools.WebTesting; using Microsoft.VisualStudio.TestTools.WebTesting.Rules; using System...
Many times when I record a web test, I do that on my local machine, the result is all the requests are directed to my localhost. A very nice feature added in Team System 2008 is the “Parameterize Web Server” button added to my Web Test GUI. Clicking on it will open a new window with one new parameter with the default name of “WebServer1”. We can also see that the “Web Server” parameter is the server that the web test was recorded on. Click OK and see that two things have happened a folder was added...
There are times when you have a part of a scenario that needs to be repeated in other scenarios. There are two options available: Record the steps each time for each of the scenarios. Create a Web Test that includes these scenario steps and embed the Web Test in other web tests. Option 2 is obviously preferable because it saves valuable time, take in account that you are not just recording steps but you also adds roles to it and modify it, wouldn’t you prefer to do that one time only? In Team System...
I have asked by clients that use the Web Test and Load Test how to add more Browsers and Network Types in order to simulate them. First I will start with how can you get to these lists. Step 1: Go to your Test Config file that is located in a solution that contains test projects and open it. Step 2: Go to the Web Test tab This is where you can find the list of “Browser type” and “Network type”. Now lets add a new network, we will call it Demo. Step 1: Go to “Program Files\Microsoft Visual Studio...
The answer to this question is defiantly NO!!! All bugs should be managed but not all bugs should be fixed . Many times when I talk with my customers about the way they develop software I hear the wrong concept of fixing all the bugs before the release. So why not to fix all the bugs? An application without bugs is not better than an application with bugs? Well lets start with a very important fact: There are no applications without bugs , there are applications that have unfound bugs . But we still...
Test Driven Development or TDD is a relatively new way of writing code. In short TDD is writing the tests before you write the code . What does it mean to write the tests before you write your code? How is that possible? To be more specific the way to do that is as follow: Step 1: Know the purpose of the code you are about to write. This step is trivial, with no requirements how can you know what to write. Step 2: Write a Unit Test that will test only one scenario in the code you are about to write...
How many times we can see similarities in different solutions comes from different companies? The answer is many... Today we can see many companies using the same features in there solutions as there competitors or even the same as features comes from solutions in different fields , you don't see many revolutionary changes between log-in solutions, on-line shops, user settings etc. So if we can see similarity with the features why not to use the same test cases that are approved to be comprehensive...
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...
A few days ago I went to a customer of mine that wants to produce a higher quality products. The main candidate for the modification was the QA group because the QA group is responsible for the quality in the development process. After a short investigation it was shown that not only the QA team should be modified but all the "players" that take part in the development process of the products should be a part of the change. Some of the conclusion were: better requirements should be written...
On the 08/09/2008 the ALM User Group gathered in Microsoft Rahanana offices. I had the honor to lecture in that gathering about the "Camano" using my experience from the Team System implementation project in Microsoft were I participate has a senior consultant . The project is the first "Dogfooding" project of the Team System "Rosario" version implementation in the world . The presentation can be downloaded from here . Enjoy!!!
In my last post "Connect your test cases to work items in Team System 2008 Test Module" I have talked about how to connect between a test to other work items in team system 2008 we have seen that there is no real connection between a test and work items, the connection is made thru the properties of the test and there is no way of creating any report using this information (test coverage report for example). But... In "Rosario" it's an all different story, the concept was...
More Posts
Next page »