Alik Levin's

Clarity, Technology, and Solving Problems | PracticeThis.com 

June, 2007

  • Alik Levin's

    Performance Testing Objectives Document Template

    • 6 Comments

    Concise performance testing objectives document helps me staying focused, save time by creating shared vision among so many hands that are in it - biz analysts representing end users, dev teams, testers, IT folks and some more. To generate simple performance testing objectives document template I used stuff found here:

     

    Here is what I have come with.

     

    I used this section to set up front the perf requirements defined in app specification. This helps making sure expectations set with the biz analysts. For example:

      • Transaction 1 Ux should take y1 sec
      • Transaction 2 Ux should take y2 sec
      • Transaction n Ux should take yn sec

    This part I used to describe the parts of the system to pay most of my attention. Today's distributed systems involve very much components - IIS, SQL Server, Active Directory, MSMQ, and more. So here I try to stay focused on what is under my control, what can be measured and tuned. This part makes sure that application architectural  characteristics have been taken into account. For example:

    This part describes network environments and hardware high level characteristics to be tested. This part makes sure that sanity check has been done with regards to environments. Helps prioritizing on resources. For example:

      • Test environment. All servers installed on one physical machine
      • Staging environment. Client machines with X configuration (CPU, memory, Servers run on virtual environment. 
      • Production environment. Got the idea...

     

    This part should describe briefly what arch changes are to be made - for example moving from Web Services to WCF, AJAX to SilverLight. This helps prioritizing on metrics to be collected that would serve to support further architectural decisions.

    This part describes exact hardware combinations to be tested.

    This part actually describes what metrics to be collected to make sure enough data collected to make decisions on one but also help reduce amount of data that adds noise, Here is the simplest example:

    Collect base line metrics (time taken) for all IIS servers  - ASP.NET UI and Web Services.

    This  part describe known stuff - pitfalls or help materials - with regards to tested application. For example links to articles or other documentation.

  • Alik Levin's

    Serviceability - Human Factor

    • 1 Comments

    There is a lot of buzz around overloaded "service" word - SOA, SaaS, Web Services, and more. There are well known and established MS names behind these too.  I ran this search to see if Serviceability (ability to provide service, I guess) is discussed. Seems like it is...

    My post is about my own serviceability - I am consultant, a service provider.

    I am trying to keep my blog strictly technical, but today I felt super strong desire to express my deepest appreciation for services that are less visible outside MS - our own Microsoft IT, the guys who help me (and all the rest MS employees) be serviceable, help me be able to provide service to MS customers == earn my pay check.

    Ran, Gili, Shachar - a HUGE thank  YOU, and Dinor - your are true rock star!!

    You guys are...    People-Ready

    I wish you all had such a great technical support team, and most important - great people.

  • Alik Levin's

    Visual Studio 2005 As General Code Search Tool

    • 7 Comments

    Visual Studio 2005 has powerful search capabilities. One of my favorites is "Find in Files".

    image

     

     

    Just hit Ctrl+Shift+F (more shortcuts - My Favorite Shortcuts).

    Essentially it uses FindStr utility that sits in System32 folder and comes for free with Windows OS. FindStr is a command line utility and those who like typing would prefer it, but those who like UI would go for Visual Studio. There is no need to open project - just fire up Visual Studio and hit Ctrl+Shift+F.

    I discussed different searching options I practice here - Security Code Inspection - Eternal Search For SQL Injection , but I thought FindStr and its utilization in Visual Studio deserves special attention.

    The best part I like is that after hitting "Find All" button I am presented with list of all files that matched the search criteria and the match itself, so I can quickly evaluate what I got in my net. Once I smell something fishy I hit the file and it opens in the very same Visual Studio for detailed inspection. I think it is very handy.

     

     Enjoy.

Page 1 of 1 (3 items)