Skip to main content

Scalability Testing

Scalability Testing is the non functional Testing. In this Testing we check the capability of the system in scale up or scale down. Scale Up and Scale down to means to check the capability of the system or Network to check the growing amount of work in order to accommodate that growth. In Scalability Testing we measure the system capability in terms of growing the workload per user, Growing the concurrent users or the size of the database.


The main goal of the Scalability Testing to determine the user limit for the web application and check the end user experienced. This is verified under the hight load.

When we test an application we are not sure the the number of user will access this web application. So in starting we prepare the 3 sets to check the load first for the basic level(Basic Load), second for the advance (Medium Load) and third one is the extended (High Load) to check the web application.

Attribute of Scalability Testing:
  • Response Time of the web server after request sent to the server.
  • Throughput
  • Hits Per Second to the particular web page
  • Request per Second onto the server
  • Transaction Per Second from the software
  • Varies Performance with varies number of Users
  • Verify Performance in High Load
  • CPU Usage during varies number of Users
  • Memory Usage during varies number of Users
  • Network Usage during varies number of Users
Labels:

Comments

Post a Comment

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.
Post a Comment
Read more

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.
Post a Comment
Read more

Difference between Error, Bug, Defect and Failure

Error: Any mistake in the coding called error. The mistake may be Syntax error, Logical errors or other GUI errors lead errors in any software. These are from developer side. Defect: The error which made by developer and during testing, Tester is able to find that errors,  means if actual result deviated from expected result then that error called defects. This is caught by testers. Bug: The defect which is developed by tester team, if expected by the developer team then that defect called an bug. Failure: If the Software does not meet the client requirement then this is called failure of the software. 
Post a Comment
Read more