Difference between functionality testing and performance

Difference between functionality testing and performance am new to software can someone tell differeence between the both if there any automation tool particular for each testing!!! thanks in advance raj

Functional testing is to test functionality of software, whether it's working(functioning) as expected or not.

Performance testing test how much load a software can tolerate.

Yes, there are automation tools available for these purpose.

For functional testing- QTP, Winrunner
For Performance- LoadRunner

Hi


Functional testing means

Consistently ensure functional correctness
Validate end-user quality
Maximize productivity by automating repetitive and error-prone tasks
Focus on meaningful testing and analysis instead of complex or fragile script maintenance
Reduce test cycles, leading to on-time and early delivery
Support more agile development processes that require frequent and faster test cycles



performance testing:

A cost-effective, easy-to-deploy-and-share solution without the typical project and application-environment limitations
Performance diagnostics built specifically for load testing
Workflow and visualization that enables quick new-user adoption and efficiency
Proven, powerful technology that is well respected in the QA industry

Hi,
Functional Testing means - to check whether the Application is behaving as per functional requirements or not.

Performance Testing means - to check how fast the functionality is being performed; which is related with time.

Functional Testing is categorized into Unit,Integration, System, End to End, Regression, Sanity, Smoke, Backend,Data Driven, Acceptance, Alpha , Beta, Secutiry , Installation and GUI Testing.

where as Performance Testing is categorized into Load, Capacity, Stress, Fail Over, Recovery, Endurance and Memory Leak Testing.

and the tools used for
Functional Testing are QTP and WinRunner,
Performance Testing is Load Runner.

Hi,

Func testing: Functional testing pertains to the testing of an application's functionality (say: when the form filled and clicked "submit" button, a message will appear saying "successfully done" and will load to relevant page). It checks whether app working as intended or not.

Perf test: It is to test the performance of the system or app on whether the app will work fine under normal conditions (Perf testing), whether it will work fine in case of simultaneous access of app by say 10000 users or heavy volume of data at a time or within an hour etc (load testing) and finally the testing of system to determine the worst conditions of app regarding its failure point on testing app for such a long time with more volume of data or more no of users etc (Stress testing) it also includes testing app under lower memory, poor network conditions etc

[B]Functional Testing [/B]
Functional testing involves testing two or more modules together with the intent of, finding defects, demonstrating that defects are not present and verifying that the module performs its intended functions are as stated in the specification. It establishes confidence that a program does what it is supposed to do.QTP is widely used tool for this.

Performance Testing
Performance testing is done with the intent of determining how quickly a product handles a variety of events, actions or functions. Automated test tools geared specifically to test and fine-tune performance are often used often for this type of testing. It is a part of load testing.LoadRunner is the widely used tool for this.

In software engineering, performance testing is testing that is performed, from one perspective, to determine how fast some aspect of a system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability and reliability. Performance testing is a subset of Performance engineering, an emerging computer science practice which strives to build performance into the design and architecture of a system, prior to the onset of actual coding effort.

Performance testing can serve different purposes. It can demonstrate that the system meets performance criteria. It can compare two systems to find which performs better. Or it can measure what parts of the system or workload cause the system to perform badly. In the diagnostic case, software engineers use tools such as profilers to measure what parts of a device or software contribute most to the poor performance or to establish throughput levels (and thresholds) for maintained acceptable response time. It is critical to the cost performance of a new system, that performance test efforts begin at the inception of the development project and extend through to deployment. The later a performance defect is detected, the higher the cost of remediation. This is true in the case of functional testing, but even more so with performance testing, due to the end-to-end nature of its scope.

In performance testing, it is often crucial (and often difficult to arrange) for the test conditions to be similar to the expected actual use. This is, however, not entirely possible in actual practice. The reason is that production systems have a random nature of the workload and while the test workloads do their best to mimic what may happen in the production environment, it is impossible to exactly replicate this workload variability - except in the most simple system.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - -- - - - - - - - - - - -- - - - - - - -- - - -- -- --

The functional tests define your working system in a useful manner. A maintained suite of functional tests:

* Captures user requirements in a useful way
* Gives the team (users and developers) confidence that the system meets those requirements

Functional tests capture user requirements in a useful way. Traditional development captures requirements in use cases. Usually, people argue about the use cases and spend a lot of time refining them. When they're finished, all they have is paper. Functional tests are like self-validating use cases. Extreme Programming methodology can illustrate this concept. XP Stories are commitments to a future conversation between the customer and developers. Functional tests are the output of this conversation. Stories without functional tests can't be built very well.

Functional tests fill in the gap left by unit tests and give the team even more confidence in the code. Unit tests miss many bugs. They may give you all the code coverage you need, but they might not give you all the system coverage you need. The functional tests will expose problems that your unit tests are missing. A maintained, automated suite of functional tests might not catch everything either, but it will catch more than the best suite of unit tests can catch alone.

Following are the differences between functionality and performance testing:

<b>In functionality testing ,</b>
a. the functionalities such as all the fields, buttons, radio boxes were tested to see it works properly
b. the application is tested whether all the fields are performing the actions which they are intended to do.
c. The system is tested as a whole where the application is tested for its behaviour as per the requirements and specifications.
d. End to end Testing is performed to validate whether the flow of actions across the module is as per the requirements.
e. is performed either manually or by using automation tools. As a start off the testing will be done manually and then will be upgraded to automation testing

<b>In perfromance testing,</b>
a. The system is validated for the performance such as load, stress, volume, localisation, spike
b. Load is tested by checking how the system reacts if there are more load applied, such as testing by 'n' number of virtual users
c. volume testing is done to validate how the system reacts for the more data storage
d. the system is validated to check how it reacts for the low memory space, very less speed etc.,
e. Performance testing is also referred as non functionality testing, where the validation is done mostly by the usage of automation tools.