Kobe is a “getting started” resource kit on planning, architecting, and implementing Web 2.0 applications and services using the Microsoft Platform.
I am sure all of you who are interested in this area would be really benefitted with it.
Check this out: http://msdn.microsoft.com/en-us/architecture/bb194897.aspx
Microsoft’s Visual Studio Team System Test Edition provides a powerful platform to perform high volume load testing. It also provides high end flexibilities to write and utilize external plug-in for extended functionalities.
Email Reporter: VSTS 2008 Load Test Plug-in enables users to send the load test reports to one or more pre-configured email addresses automatically, once a VSTS Load Test is completed. This open-source load test plug-in also provides supports for customization by which you can customize the reported performance data.
Download the latest version from: http://code.msdn.microsoft.com/erep
Roy Osherove written an excellent ‘Restaurant’ analogy to explain the difference between unit tests and integration tests. This type of analogy really becomes lot helpful to understand the concepts that are similar to each other, but has significant difference as well as.
In the world of testing, Smoke Testing, Sanity Testing and Regression Testing are very similar to each other: to ensure the quality running the test cases of an existing application with respect to a new feature being added/dropped/modified. They are targeted to find out the bugs in both UI and code level.
We can consider a River Analogy to understand the difference between Smoke Testing, Sanity Testing and Regression Testing better. Before moving to the analogy, lets consider the very basic definition of three of these testing:
- Smoke Testing: Testing all (wide) areas related to new feature, not deeply. Determines if we should go for further testing.
- Sanity Testing: Testing narrow areas related to new feature, deeply.
- Regression testing: Testing all areas related to new feature, deeply.
If we consider a river, for instance, which has, for instance 1000 feet width, and contains “dusts” in its water (which can be considered as “bugs” in software), the goal for the corresponding three types of tests should be as follows:
For Smoke Testing: to find out the dusts in all over the surface of the river, which not includes the dusts under water.
For Sanity Testing: to find out the dusts in a specific width (for instance left side 200 feet), which not only includes the dusts on surface, but also includes the dusts under water, till the last depth of the river.
For Regression Testing: to find out all the dusts that are available on surface and under the water in all over the river.
ASP.NET Developers, Bangladesh is a group of professional developers, which focuses the latest development trends in ASP.NET and it’s related technologies. This professional group is member of INETA (International .NET Association) and Culminis.
The previous group site address has been changed, as it was hosted at MSN group, which was closed from March 2009. All of the previous group members and those who are not yet been member but interested to share and learn new cutting edge technologies are requested to join in the new site:
The new site contains lots of resources including blogs, discussion forum, media gallery, code gallery etc.