NonFunctional Testing

Non Functional testing is a part of checking the stability in the application, for instance how does the variables reflect if the data entered is not relevant to the data which specified. non functional testing involves adhoc testing process to check the stability. 

It also involves different ways meaning it can be testing the acceptance after changing the environment changing the popup messages etc.

Performance Testing:

Performance tests are used to evaluate and understand the application’s scalability when, for example, more users are added or the volume of data increases. This is particularly important for identifying bottlenecks in high usage applications. The basic approach is to collect timings of the critical business processes while the test system is under a very low load (a ‘quiet box’ condition) and then collect the same timings with progressively higher loads until the maximum required load is reached. For a data retrieval application, reviewing the performance pattern may show that a change needs to be made in a stored SQL procedure or that an index should be added to the database design. Stress Testing – Stress Testing is performance testing at higher than normal simulated loads. Stressing runs the system or application beyond the limits of its specified requirements to determine the load under which it fails and how it fails. A gradual performance slow-down leading to a non-catastrophic system halt is the desired result, but if the system will suddenly crash and burn it’s important to know the point where that will happen. Catastrophic failure in production means beepers going off, people coming in after hours, system restarts, frayed tempers, and possible financial losses. This test is arguably the most important test for mission-critical systems.

Load Testing:

Load tests are the opposite of stress tests. They test the capability of the application to function properly under expected normal production conditions and measure the response times for critical transactions or processes to determine if they are within limits specified in the business requirements and design documents or that they meet Service Level Agreements. For database applications, load testing must be executed on a current production-size database. If some database tables are forecast to grow much larger in the foreseeable future then serious consideration should be given to testing against a database of the projected size.

Recovery Testing:

If the system crashes then change the hard disk to the different system and it should be a recovery from the hard disk and apply the recovery scenarios.

Fail-over Testing

This type of testing validates a systems ability to be able to allocate extra resource and to move operations to back-up systems. This type of testing is used to verify an IT systems ability to continue operations while the processing capability is being transferred to a back-up system. This type of testing determines whether a system is able to allocate extra resource such as additional CPU or servers during critical failures or at the point the system reaches a predetermined performance threshold.

Security testing:

is performed to check whether there is any information leakage in the sense by encrypting the application or using wide range of software’s and hardware's and firewall etc. Before planning for Security Testing, you will need to think about the following parameters:

• Authentication - Testing the authentication schema means understanding how the authentication process works and using that information to circumvent the authentication mechanism. Basically, it allows a receiver to have confidence that information it receives originated from a specific known source.

• Authorization - Determining that a requester is allowed to receive a service or perform an operation.

• Confidentiality - A security measure which protects the disclosure of data or information to parties other than the intended.

• Integrity – Whether the intended receiver receives the information or data which is not altered in transmission.

• Non-repudiation - Interchange of authentication information with some form of provable time stamp e.g. with session id etc.