What is Performance Testing

Performance Testing

Testing the stability and response time of an application over a period of time by applying the load of data is called Performance Testing.

Here load of data may be: Number of users or it may be volume of data

Why Do Performance Testing?

At the highest level, performance testing is almost always conducted to address one or more risks related to expense, opportunity costs, continuity, and/or corporate reputation. Some more specific reasons for conducting performance testing include:

• 1.      Assessing release readiness by:

1. Enabling you to predict or estimate the performance characteristics of an application in production and evaluate whether or not to address performance concerns based on those predictions. These predictions are also valuable to the stakeholders who make decisions about whether an application is ready for release or capable of handling future growth, or whether it requires a performance improvement/hardware upgrade prior to release.

Difference between Functional and Non-Functional Testing

Functional Testing: 

1. Testing the application against business requirements. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.
2. Functional testing is concerned only with the functional requirements of a system or subsystem and covers how well (if at all) the system executes its functions. These include any user commands, data manipulation, searches and business processes, user screens, and integrations.
3. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.

what is Ad-hoc and Exploratory Testing

Ad-hoc Testing

1. Ad hoc testing is a commonly used term for software testing performed without planning and documentation.
2. The tests are intended to be run only once, unless a defect is discovered.
3. Adhoc testing is the least formal test method.
4. The strength of ad hoc testing is that important defects can be found quickly.
5. A creative and informal way of testing the software
6. Conducted without any understanding of the software before testing it
7. Not conducted based on formal test plans or test cases
8. Performed by Testers
9. Performed on a Stable application or product.

Difference between smoke testing and sanity testing

Smoke Testing

Software Testing done to ensure that whether the build can be accepted for through software testing or not. Basically, it is done to check the stability of the build received for software testing.

In Smoke Testing, the test cases chosen cover the most important functionality or component of the system. The objective is not to perform exhaustive testing, but to verify that the critical functionality of the system are working fine.

For Example a typical smoke test would be - Verify that the application launches