Performance Testing

Performance Testing

      Performance Testing is the process for primarily used to determining capacity of existing systems and  creating benchmarks for future systems and evaluating degradation with various loads and/or configurations.It increase the speed , scalability , stability and confidence.

 Benefits of Performance testing 

• A system is ready for release into production.
• A system is likely to meet its goals.
• Resources are being used effectively 

Type of Performance Test

• Load test : Testing of a web site under a range of loads to determine at what point the system's response time degrades or fails .

• Stress test : Its conducted by keeping the static concurrent system accessing the single business transactions repeatedly.

• Scability Test : Testing is done by dynamically increasing the concurrent 
  users to access the business transaction against static data to monitor 
  the response time.

CLIF

It is distributed load testing tool and it help to measure the web application directories , services ,databases and telecommunication .

Power of Load Injection 

• Can successfully tested with up to 1300 load injectors.
• Can successfully tested with more than 10 millions of virtual users.
• Can transparent distribution support: centralized deployment, control and monitoring of probes and load injectors, and final collection of measures.

Type of User Interfaces 

• Full-fledged Eclipse-based, or simple Java-swing graphical user interfaces.
• Embedded analysis and reporting tool.
• Full-featured ant-based or maven-based command line interface.
• Hudson/Jenkins plug-in for automatic load testing in continuous integration.

Load Injectors 

• HTTP(S)
• FTP
• TCP
• UDP
• LDAP
• SIP
• RTP

Resource Probes

• CPU
• Memory
• Jvm
• Network
• disk

Requirement 

• java 1.5+
• Apache ant 1.8+
• Eclipse 3.3+

The future

Tester need to create test cases and file the bugs and create test plans with the artifacts, the artifacts sense creates secondary source code and it provides a value to tester activity. So separate team of testers they need to construction and maintains the test artifacts.

According to the Google ; future roles of test department people’s, briefly describing below:

Types of Google test department:

•        Software Test Engineer
•          Test Engineer
•          Test Director and Manager

The future of Software Test Engineers(SWT)

In google, SWT is a developer mean they played same role as software engineers and followings are their features:

•     Testability
•     Reliability
•     Debugging capability

In Google, they can simply convert SWT to the SWE and there is no difference in the titles of the engineers involved, there are no barriers to moving from test to feature development.

The future of Test Engineer(TE)

TEs have the following responsibility

•          Test cases creation
•          Test cases execution
•          Done the regression testing

And it is a traditional role of testing and TE can move to following categories of expertise:

•  Security
•  Privacy
•  Performance
•  Exploratory testing

These are more challenging and senior role and it give the opportunities to great deal with expertise.

The Future of the Test Director and Manager

It gives the change to TE and SWT. They will lead and coordinate the both TE and SWT and also fused the quality of the SWE. They have the responsibility to handle the test activities in accountable manner.

The test infrastructure has been moved from manual test to automation test. In Google, they use the selenium and web driver for test automation. Nowadays Test infrastructure developers more visibility and most importantly.

Reference 

How Google test software