Tech Notes

For a recruiter sourcing performance testing profiles, filtering relevant profiles is one of the most challenging task. They need to have better job description and set of questions to take informed decision. This article provides pointers around this. There are many steps involved for sourcing the profiles but here in this article, two important steps will be discussed in detail. (1) Initial Screening of Resumes (2) Initial Phone Screening. The Initial Screening of Applications and Resumes In this step, applications are screened to see if they meet minimum qualifications for the job. The goal is to weed out fake profiles, below average profiles and profiles not matching the existing job openings. Below criteria can be used for initial screening of performance testing profiles. P = Performance Engineers L = Performance Leads A = Performance Architects Criteria Description Relevant Experience It is one of the most important criteria for filtering during the initi

For a vendor offering performance testing service, submitting a competitive proposal and winning pursuits is not an easy task.  Submitting a proposal usually requires approach, estimate, cost and assumptions for the engagement and it’s a challenge for service vendor to get this information correct in less time with minimal information available at hand.  It is seen that sometimes vendor ask their prospective customers lots of questions, which might not be relevant for preparing the proposal but might be good for the overall performance testing engagement.  In this article, I will discuss minimal set of questions that should be asked and importance of these questions for preparing the proposal.  These questions are not the only questions and based on the answers, further relevant questions can be asked. Project Context / Testing Objectives Question Notes Please provide business overview of Application under test It helps in understanding the application’s domain and its as

Traditionally performance testing approach usually follows Identification of Key Scenarios, Setting up the Load Environment, Designing the Scripts, Generating load, Monitoring and at last Analysis and Reporting.   It works for most of the system but it is completely a different ball game when conducting performance testing of large scale distributed system.   In this article, some of the key characteristics and challenges will be discussed for performance testing of large scale distributed system. Key Characteristics High Volume »         Terabyte of transactional records in database »         Network throughput in gigabits per second High Transactions »         Millions of transactions per second from end users »         Millions of transactions in database due to few triggers (e.g. large report generation due to batch processing) High Concurrency »