Performance Testing Questionnaire Template

For latest article on this topic, please check here
1.         Project Context 
What is the system needed for? (Brief description of project)





Who are the end users of the system?





Do you have any existing performance concerns?





When would you like to start the assignment?  When would you like to finish it?





Domain (useþ)

o Retail                        o Insurance                              o Healthcare
o Avionics                    o Real time/Embedded             o Enterprise E-Biz
o Games                      o Others (Please specify: ____________________)
o BFSI

Technical (useþ)

Type of application
o Client Server                         o Web Application                    o Multimedia               
o Consumer Electronics             o Others (Please specify: ____________________)

Architecture of the system (2/3 tiers): _____________________________________

Technologies used

Front End (e.g. SilverLight, flash)

Middle Tier (e.g. asp.net, PHP)

Backend (e.g. MySQL, SQL server 2008)

Protocol used for communication (e.g. http)

Others (e.g. VPN)


Load Profile

No. of simultaneous users / No. of Concurrent users
(Simultaneous users have active connections to the same Web site, whereas concurrent users hit the site at exactly the same moment. Concurrent access is likely to occur at infrequent intervals. Your site may have 100 to 150 concurrent users but 1000 to 1500 simultaneous users)

Different type of requests and requests / sec
(e.g. for a scenario X,
Login, 25 request/s
Search, 50 requests/s
Logout, 25 requests/s)


Network bandwidth desired (in Mbps)
(Network bandwidth varies as per requests and response size)

Maximum number of records in database
(Baseline database size in terms of records, which needs to be established before conducting the performance run)



SDLC (useþ)

What is the current phase of SDLC?
o Requirements                        o Design                      o Coding
o Deployment                           o Maintenance              o Enhancement

Documents

Please select the documents that can be shared to Performance Team

Document
Available (To Company)
Project Documents

Physical / System / Logical Architecture
o Yes    o No
Users Manuals
o Yes    o No
Business Model / Flow
o Yes    o No
            Deployment Instructions
o Yes    o No


Performance Testing Related

            Business Key Scenarios
o Yes    o No
Performance Goals and Requirements
o Yes    o No
Benchmark Specifications
o Yes    o No
Capacity & Sizing guide
o Yes    o No
Existing Performance Testing Artifacts
o Yes    o No

2.         Performance Testing Purpose

Purpose of the performance testing (select all that apply)

o Establishing baseline for future releases
o Analyze the behavior of the application at various load levels
o Ensuring the functionalities doesn't break under stress
o Determine failure point of the application
o Determine the endurance (load testing for longer run) capabilities of application
o Determine compliance with performance goals and requirements
o Reporting benchmarking results to outside
o Identifying bottlenecks in a system
o Collecting data for scalability and capacity planning
o Others (Please specify: _____________________________________________________)

3.         Test Environment

Performance Test Environment (useþ)

o Production environment scaled down (If so, by what proportion?)
o Production replica

Dedicated Test Environment available (useþ)

o Yes               o No

Test Team Location (useþ)

o Onsite           o Offshore       o Onsite/Offshore

Availability of Load Generation Tool (useþ)

o Yes (Please Specify the Tool Name)                                   __________________________
o No (Any preferences? Open Source / Free / Licensed)        __________________________

Comments

Post a Comment

Popular posts from this blog

Performance Test Run Report Template

You have gathered requirements from clients, identified key critical business scenarios, analyzed the workload distributions, found out performance goals and requirements, identified  tool for generating load, setup the test environment, designed the scripts, executed the performance run, collected the raw data, analyzed it, what next?  Send information to stakeholders? No!!  Wait!! It needs to formatted, customized for different stakeholder(s) and reported accordingly. This article suggests one of the ways to report performance run results to client especially if the performance testing activity has been outsourced to yours company.  It discusses the performance report template and importantly the reasons for including the items in the report. The performance report template contains information by data collected from client side only and doesn’t discuss / talk about data from server side like processor utilization etc. Broadly the performance report has been divided in three major
Read more

Understanding Blockchain

This notes will cover below questions... Introduction to Blockchain What is the difference between Blockchain and Bitcoin? What are some other uses of blockchain that go beyond bitcoin? History of blockchain Could you explain the blockchain process in laymen terms? If all data is available to the public. Can anyone know my bank balance (in Bitcoin)? Introduction to Blockchain The Blockchain is a decentralized and distributed public (digital) ledger where transactions are recorded and confirmed anonymously. It’s a record of events that is shared between many parties. More importantly, once information is entered, it cannot be altered without altering subsequent blocks. WTF is the blockchain? A guide for total beginners What is the difference between Blockchain and Bitcoin? The blockchain is a technology
Read more

Bugs Management in Agile Project

Agile has a refreshing approach to bugs, especially when contrasted with traditional waterfall practices. Historically, teams would postpone bugs to a stabilization phase. This stabilization phase was long and tedious, typically with high stress and long hours. Agile, on the other hand, promotes the following thought processes: Carrying bug debt is unhealthy and sometimes, even destructive. We should fix bugs, not track them. A feature isn't done until the bugs are fixed. Quality is part of the overall cost. Bugs are prioritized against new features. A bug needs to be more important than the next new feature. Notes All new features have a "bug tail." The bug tail is the diminishing number of open bugs on the new functionality. When a feature is added, bugs are introduced. Most are discovered and fixed immediately by the team as a part of feature development: some a few days later, others not until long after a story is considered &quo
Read more