Performance Testing Activities


In any performance testing projects, following are commonly performed activities.  These are not the exhaustive list though but covers majority of them.


Discovery Phase
  • Identification of critical business scenarios
  • Identification of frequency / workload distribution of known scenarios
  • Finalizing network bandwidth and geo-location for workload distribution
  • Assessment of performance testing tool for the assignment
  • Finalization of performance testing goals and requirements
  • Developing network topology for SUT (system under test) and load generation environment
  • Identifying number of hardware and its configuration
  • Identification of licensed software


Design Phase
  • Procurement of required hardware and software
  • Setting up of SUT lab & verification
  • Setting up of load generation lab & verification
  • Performance test planning
  • Preparation of test data being utilized in scripts
  • Scripts designing
  • Population of (production like) test data in the database


Execution Phase
  • Setting up the monitoring tool
  • Smoke run and report generation
  • Execution of different types of performance run for certain duration
  • Collection of performance metrics / counters


Analysis & Reporting Phase
  •  Preparing the report
  •  Analyzing the graphs / data present in the report and provide accordingly recommendations, pointers, observations etc.
  • Uploading / Store all performance testing artifacts at shared location

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 divi...
Read more

Best Practices for Unit Test Case Automation

Make each test orthogonal (i.e., independent) to all the others Any given behavior should be specified in one and only one test. Otherwise if you later change that behavior, you’ll have to change multiple tests Don’t make unnecessary assertions Which specific behavior are you testing? It’s counterproductive to Assert() anything that’s also asserted by another test It just increases the frequency of pointless failures without improving unit test coverage at all Have only one logical assertion per test Unit tests are a design specification of how a certain behavior should work, not a list of observations of everything the code does Test only one code unit at a time Architecture must support testing units (i.e., classes or very small groups of classes) independently, not all chained together If you can’t do this, then your architecture is limiting your work’s quality – consider using Inversion of Control Mock out all external services and state Yo...
Read more

How to Report Bugs Effectively

As per defined in wikipedia – “A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's source code or its design, and a few are caused by compilers producing incorrect code. Reports detailing bugs in a program are commonly known as bug reports, fault reports, problem reports, trouble reports, change requests, and so forth.” There might be many fields (information) need to be filled while reporting a bug.  The number of fields, mandatory fields, optional fields etc. differs from team to team.  But few bare minimum fields that are required during reporting a bug in almost all teams are as follows: Title Description Steps to Repro Expectation Severity / Priority Most of the time, testers go and try to provide these information in hurry,...
Read more