Showing posts with label performance testing. Show all posts
Showing posts with label performance testing. Show all posts

Friday, April 15, 2016

Jenkins for Automation and Performance Testing - DevOps QA

Jenkins an open source continuous integration utility developed using Java

Continuous integration features of Jenkins is being used by QA team very robustly. Automation QA team needs to validate build for consideration of Regression Testing Go/No Go. Jenkins being used to validate the build status and stability by exciting JAVA scripts converted and configured as JAR and executed via command lines.

QA Team also use Jenkins to do performance testing by executing Jmeter scripts configured as job and servers as slaves.


Core Features
  1. Continuous Integration and Continuous Delivery
  2. Easy installation
  3. Easy configuration
  4. Plugins
  5. Extensible
  6. Extensible
Steps to Start: 

  1. Download Jenkins
  2. Identify Scenario
  3. Download and Discover Plugins
  4. Create Jobs
  5. Execute
  6. Analyse
So now we can consider Jenkins as new tool to be used by Automation QA and now can be converted as DevOps QA



Monday, June 15, 2015

Performance Testing & Load Runner

Performance Testing:

Performance testing is the process of determining the responsiveness or effectiveness or scalability and stability of software or device to determine how the components of a system are performing with given a particular state.

It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.

It includes: Load Testing, Stress Testing, capacity testing, volume testing, endurance testing, spike testing, scalability testing and reliability testing etc.
This type of testing does not give pass or fail result, it performed to get benchmark & standard of the application against Concurrency / Throughput, Server response time, Latency, Render response time etc. for responsiveness, speed, scalability and stability characteristics.

Load Runner has 4 key components

1. Virtual User Generator (VUGEN)
VUGEN is used for generating and editing scripts
It has four components
1)    Record
2)    Run
3)    Debug
4)    Design

2. Controller
Controller is where we apply the load. The Controller systematizes drives, manages and monitors the load test.
3. Load Generator
Load Generate is local CPU which generates the load by running virtual users
4. Analysis
Analysis accumulates logs from various load generators and present reports for visualization of run result data & monitoring data
Load Runners shows error details as below.
1) Syntax error: [ , ; : “ ) ] etc.
2) Runtime error: Spelling error.
3) Compiling error:

Advance Components

·         Parameterization
Replacing the recorded value with a script value.The value that you are replacing has to be in the database
          Parameterization helps
1.    Reducing script size
2.    Avoiding cache effect

·         Correlation
Using “Correlation” we can capture the dynamically generated value from the server using nested queries.

·         Load Balancing
How to increase/decrease the load

·         Think time
Think time is the time that a real user waits/ pause between actions.

·         Rendezvous Point

Rendezvous Points means “meeting points”. This option used to check the peak load from off peak load. Virtual users instructed/configured to wait during test execution for multiple Vusers to arrive at a certain point before execution