Friday 31 May 2013

Basic Web Performance Part 2


In last article we saw the importance of better performing Web site . So we need to make sure that our sites are performing better but before we work on improving the performance we need tool to measuring  the Web site performance. In this article and series of next articles we will talk about few tools which will help measure the performance . Here is list of tools we we look at.

1. Fiddler
2. Microsoft Network Analyzer
3. IIS Log files
4. 3rd Party Services

While we will have a look on top three we will not talk about the fourth one which is basically services that benchmark your web site against the different web sites. So lets start with Fiddler.
We touched upon some of core feature of Fiddler ; lets get started with practical. I will hit upon Microsoft.com and Fiddler will then capture and we will start analyze the data through various functionality provided by fiddler. Below is the screen shot of the request which gets generated upon hitting microsoft.com.


Timeline provides the graphical representation of the request response times .The data captured through the Fiddler can be saved for later reference. In image above the right panel shows the timeline , as you can see the aspx page got loaded in 2 seconds but the other  content on the site took 14+ seconds; which shows most of time is spend on downloading static resources.

There is another feature which is called Statistics which apart from other details lets us know the response bytes (by Content type) against the content which can determine the most consuming bandwidth data that can be looked upon for optimization.
 In above figure you can see the maximum bandwidth is used by the jpeg files and those are good sources of optimization.

Thursday 30 May 2013

Basics Web Performance -Part 1

Basics Web Performance

We need to know why do we care about the performance. While fast web sites makes customer happy there are other benefits of better performance , They  saves your money by

1. consuming less bandwidth
2. Consuming less servers

Better performing websites also help in generating more money ,

According to recent survey done on two web site Google and Amazon ; In amazon it was observed with every 100 ms increase in load time of Amazon.com the sales got decreased by 1% in another incident the home page of goggle maps when decreased from 100KB to 70-80KB traffic went up by 10% in first week and additional 25% in following three weeks.

Your web site performance also impact the ranking on Google. Now we know the importance of performance lets have a look at what makes web sites slow

The general assumption is the performance of website can be improved by tuning the code on server side.But with recent research it has been found that 10-20% of total response time is invested in processing the request  generating the HTML and getting it download. While rest of 80-90% time is invested on getting auxiliary files like image , javascripts, css etc. To demonstrate this we need to use the tool to see the conversation that happen b/w the browser and server. The conversation between the browser and server happen through HTTP protocol . The protocol stands for Hypertext Transfer Protocol ; it is text based protocol so we need some tool which can help profile http traces and one of the tool is Fiddler. This tool can watch the conversation that happen b/w browser and server

This tool is free and can be downloaded by doing small search on google ; The tools has various features

1. You can watch the web traffic
2. Shows complete request and response
3. Can save the session which can be used to compare the performance before and after
4. Transfer Timeline : graphical view of all the request made
5. Statistics is another feature in Fiddler.

We will talk about the fiddler and how we can see the response time on next post.....

Monday 20 May 2013

Menopause Testing

In each Profession with experience task gets more repetitive , mundane  , less challenging, boring . There comes a day/week/phase which is like menopause ? The focus changes from core profession task with no creativity to people management , other skills focus , changing stream etc. IT Profession is no different in this aspect. The software development , testing all goes through the phase and person has to be prepared for this.

This phase also has challenges for the organization people start to leave to find something new in another organization , less motivated people becomes complacent which results in more mistakes and lesser productivity. People having enough time on planned task and invest time on office politics and other non core focus areas.How does organization make use of this phase is challenge.

While organization takes a different route and more specific with each organization type services vs Product , large size vs small size etc. I will talk more at individual level how you can take charge of your career at this phase. I would recommend to invest time on training , connecting through forums , participating in  Test Competition, writing testing blogs etc.

The training would give you an edge over others in your subject. Since our tasks mainly focuses on specific features we tent to use 10-20% of the features only while rest 80% is never used. This is more like pareto where 20% of feature solves your 80% problem . Enrolling in Bug finder sites will give adrenaline boost as it involves some extra money too depends on which phase your application is in you can get paid for each bug you find.

Test competition is another way you can get your skills toned and learn about the techniques and tools with little risk involved.

Friday 10 May 2013

My First International Test Competition Experience

A month or more back when i logged on my Linkedin Profile ; i saw something happening as part of Competition. Initially i thought it was Performance test competition.working on performance i was excited to learn about the different perspective/tool  of testing and hopefully chance to Win !! I decided to participate; I enrolled and started looking out for the team members. Though  we could confirm the team 2 weeks before the competition from different location in India.

Test Competition information was on NRG global blogs ; we started going through the blogs to know when/what/how and having read all the details we had still queries and confusion  and then we started out first discussion with Matt with set of Queries this lasted with spawn discussion about the reporting tools , Apploader ,  performance queries,architecture questions etc with different peoples . I am not sure  if they really loved to answer all queries posted by us but thanks to  Matt , Dan, Ben Smita  and other associates who patiently responded all our queries.

Though our initial discussion we were aware about the competition process and we know we had 3 hours to get requirement , test, file bugs , create  reports, suggest recommendation etc!!. HMM .. too much to be achieved in 3 hours and considering team of two people we had tough task! After thought we could have atleast team of 3 people should have helped better.

The competition day and time arrived Matt posted a blog just before the competition and we went through the blog , asked few specific requirement question  finalized on Test Scope and strategy and started on finding bugs!! One of most confusing part was different communication medium like skype,hangout,twitter, you tube etc..where people were interacting with Matt and most question were repetitive , people even discussing bugs though it was only meant for requirement discussion!!

We decided on QuickEasySurvey.com and CorkBoard.me  to be functional tested out of four website and now i think we made good decision. We focused on bugs and had enough number of them but somehow we logged them as one liner in the Team Pulse. I think we have not done good job of reporting  (at least on QES , my team mate still did better job on CorkBoard.me). The functional testing report on quality and recommendation were suggested .We  were running late , compiled the report and pushed it as fast as possible!! hmm still late by few minutes not sure how many points we have lost!!

The next day was planned for the Performance Testing ; we have finalized on the website and time slot we had lengthy with Dan about the application architecture and areas we want to focus on. Post the discussion we came to know this will not give the right performance metrics through Jmeter as there were lot of client side scripts and Jmeter does not behaves like the browser and had limitation there! Having though of pros and cons of performance tool we decided to go ahead with Apploader!!

There was lengthy process of setting up Apploader , generating scripts , Azure set-up . Though every thing was free but as usual all is not free and we ended up paying 1$ for Azure for International card usage :-)

After all hurdles and support from Ben we could run 25CC test and could gather the application performance as gave recommendations for performance . This all took a week post the competition and we were very tired with all night outs due to different time Zones :-) Many time we thought to leave but we persisted as support from Ben was always there. All thanks to my team member Anindita to taking this to closure.

After the competition and all reports submitted we awaited for results !! Hoping to Win and Learn. The results arrived and we were not as best as others but still we got good feedback on certain areas where we did better than others.


http://www.nrgglobal.com/general/test-competition-results


We would like to congratulate all the teams who have won !

There is lot of takeaways from the competition and we hope to utilize these learning for future!




Thursday 9 May 2013

My First Blogging Experience

When did you first blog ?? during college ,after  few years in jobs or  never !! Though i remember i wanted to start blogging few years backs not sure though which year .

But finally it happened today and i am lucky that i have done it for good ; what it takes to start a new blog 6 min of video and that all :-) i am not sure why i waited so long for this!!

My blog address testerkpi.blogpost.in got a name after my affilication with Analytics and Business Intelligence application and also term coined during the team meeting which we have during this week ! Well done the video helped to create the blog and a post..next how to add more post tough!! got it and this is how this post happened. Added the details about me , location details and also confused all the integrated application that google provides Google Plus+ , blogger, gmail and integrated data shared across these application. Still many tools needs to be added to the blog site need to watch out few more videos and enhance for better user experience.

Tester KPI

Confused over how to rate yourself as tester ? what are the key indicators for functional , non functional tester.

 A good coding skills, documenting skills, interfacing skills, attention to detail, more number of  bugs , analyzing bugs and proving resolution , generating  good scenarios , finding bugs in quality cycle earlier through review are some of the things one should look for before defining the KPI.

Or are there bunch of another things like number of  number test cases or effective number of test cases  number of requirement works against , effective reporting . The quantifiable metrics may or may not be the best approach to define the KPI.

The are more adjective applied to different tasks and how to evaluate these. Say number of test cases and effective number of test case . How to say which metrics is good KPI for the tester. How do you evaluate these metrics. One approach would be to review the same but then who review all the test cases ; another way would be reverse engineering through bug leakage  then again it takes time and probably you are too late .

Through i am not against the quantitative metrics for KPI  but i think these same can evaluate your good tester as bad and vice versa. So just have caution before you proceed with metrics