 |
VOOZH | about |
|
VOOZH | about |
Testing is an important phase in SDLC that checks software for bugs, performance, and usability issues before release. It ensures the application works correctly and efficiently, helping maintain quality and user trust.
Performance Testing is a type of non-functional testing that evaluates the speed, stability, responsiveness, and scalability of an application under different workloads.
Example: Checking whether an e-commerce website can handle 10,000 users simultaneously during a sale event.
Functional Testing is a type of testing that verifies whether the application's features and functionalities work according to the specified requirements.
Example: Verifying that the login page allows users to log in with valid credentials and displays an error message for invalid credentials.
| Feature | Functional Testing | Performance Testing |
|---|---|---|
| Definition | Testing that checks whether the software works according to requirements | Testing that checks how fast, stable, and scalable the system is under load |
| Main Focus | Functionality of features | Speed, response time, stability, and scalability |
| Objective | Validate “What the system does” | Validate “How well the system performs” |
| Test Type | Black-box testing | Non-functional testing |
| Key Question | Does the feature work correctly? | Does the system handle expected and peak load? |
| Examples | Login works, payment works, form submission works | App performance under 1000 users, response time under heavy traffic |
| Tools Used | Selenium, QTP, TestNG, Postman | JMeter, LoadRunner, Gatling |
| When Performed | During every build or feature release | After functional testing, before release or major deployment |
| Test Data | Uses normal test data | Uses large volumes of data and virtual users |
| Outcome | Pass/Fail based on expected behavior | Metrics like response time, throughput, CPU usage |
