Difference between load and stress testing

Load testing is to test that if the application works fine with the loads that result from large number of simultaneous users, transactions and to determine whether it can handle peak usage periods.

Stress testing is a form of testing which is used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. For example, a web server may be stress tested using scripts, bots, and various denials of service tools to observe the performance of a web site during peak loads. Stress testing a subset of load testing.

 Performance testing:
Web application should sustain to heavy load. Web performance testing should include:
Web Load Testing
Web Stress Testing

Test application performance on different internet connection speed.
In web load testing test if many users are accessing or requesting the same page. Can system sustain in peak load times? Site should handle many simultaneous user requests, large input data from users, Simultaneous connection to DB, heavy load on specific pages etc.

Stress testing: Generally stress means stretching the system beyond its specification limits. Web stress testing is performed to break the site by giving stress and checked how system reacts to stress and how system recovers from crashes.
Stress is generally given on input fields, login and sign up areas.

In web performance testing web site functionality on different operating systems, different hardware platforms is checked for software, hardware memory leakage errors,

What is the priority and severity of the bug? Explain with example a scenario, With high priority and low severity and vice versa.

Severity of a bug describes the impact of a bug.

Blocker: Blocks development and/or testing work
Critical: crashes, loss of data, severe memory leak
Major: major loss of function
Minor: minor loss of function, or other problem where easy workaround is present
Trivial: cosmetic problem like misspelled words or misaligned text
Enhancement: Request for enhancement

Priority describes the importance and order in which a bug should be fixed. This field is utilized by the programmers/engineers to prioritize their work to be done. The available priorities range from P1 (most important) to P5 (least important.)

Example: Any look and feel issues like spelling mistake on an UI is less severe, but if the product is going for beta testing, priority of bug to fix is higher.

Similarly any exception coming on a particular operation has high severity, but that module is not to be delivered right now, so this bug can have low priority

How can it be known when to stop testing OR When do you stop testing ?

This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:

Deadlines (release deadlines, testing deadlines, etc.)

Test cases completed with certain percentage passed

Test budget depleted Coverage of code/functionality/requirements reaches a specified point Bug rate falls below a certain level Beta or alpha testing period ends

How to define your roles and responsibity in testing?

My role starts from very initial phases of the release. It is May responsibilities to create list of use cases on the basis of the requirement discussed.

I need to be closely involved in the Technical discussion of a feature with the developers. This helps me to create the checklist of functionality later create the test case and excuted test data.

What is the general testing process?

Testing Process:
1. Test requirements analysis
2. Creation of Test Strategy
3. Creation of Test Plans
4. Execution of test cases
5. Analyze the test results
6. Report the defects if any

If there is no sufficient time for testing & u have to complete the testing, then what will u do?

When I have less time to test the Product then I will take these following steps—

1) Sanity or smoke testing
2) Usability Testing
3) Formal Functionality and GUI Testing
4) Walk through with the Product

What is difference between application testing and product testing?

Product testing means when any company does testing for their own product.
example: Norton Antivirus is the Symantec’s product; if Symantec test the Norton i.e. called As the Product testing.

Where as if any company take some projects from some other Companies like ABC Company takes projects from IBM and test that project on some charges i.e. called as Application Testing.

What is a broken link in web testing and how test it?

When we clicked on hyperlink if it opens "Page can’t be displayed" then that Hyperlink is called as broken link.