SIA LESSON 4 - TYPES OF TESTING

FUNCTIONAL TESTING

Testing verifies that the software performs the functions specified in the requirements. "Does the software do what it is supposed to

- Verify system functionality against specifications

- Ensure compliance with requirements

- Assess adherence to business rules

- Validate accuracy of inputs and outputs

NON-FUNCTIONAL TESTING

"How well does it work?"

testing looks at quality factors like performance, usability, reliability, security, compatibility, and maintainability.

NON FUNCTIONAL - Performance Testing

Can the Enrollment System support 5,000 students logging in at the same time?

Speed | Response Time | Scalability

NON FUNCTIONAL - Security Testing

Can hackers access another student's grades?

Authentication | Authorization | Data Protection

NON FUNCTIONAL - Usability Testing

Is the interface easy to understand? Can first-year students enroll without confusion?

NON FUNCTIONAL - Reliability Testing

Can the system run continuously for several days without crashing?

NON FUNCTIONAL - Compatibility Testing

Is the system compatible with Chrome, Firefox, Edge, Android, and iPhone?

Confirmation Testing

IT ensures that a specific defect has been resolved.

• when users clicked Submit Enrollment, causing the application to crash.

• After the developer fixed the problem, the tester ran the same test again.

• The expected result is that enrollment completes successfully without any issues.

Regression Testing

This testing ensures that recent changes haven’t introduced new bugs into existing features.

developer fixes the Payment module; they also test login, Shopping Cart, Checkout, and Order History to make sure that everything still works

Functional Testing

A tester verifies that users can successfully log in using valid credentials.

Non-Functional Testing (Performance Testing)

A tester measures whether the website loads within 2 seconds during peak hours.

Confirmation Testing (Re-Testing)

After a login defect is fixed, the tester executes the same login test again to verify the fix.

Regression Testing

After updating the payment module, the tester checks the shopping cart, checkout, and order history to ensure they still work correctly.

Non-Functional Testing (Security Testing)

A tester checks whether only authorized users can access the Admin Dashboard.

Non-Functional Testing (Compatibility Testing)

A tester checks whether the mobile application works correctly on Android and iOS devices.

Functional Testing

A tester verifies that clicking the "Cancel Order" button correctly updates the order status to "Cancelled" in the system and refunds the payment balance.

Non-Functional Testing (Performance Testing)

A performance tester simulates 10,000 users searching for products simultaneously to observe if the database response time stays under 1 second.

Confirmation Testing (Re-Testing)

A bug was reported where the profile picture failed to upload on the settings page. After the developer released a fix, the tester uploads a profile picture again to confirm the bug is resolved.

Regression Testing

After modifying the checkout feature, the tester checks the product search, user registration, and wishlist features to verify nothing was broken by the update.

Non-Functional Testing (Security Testing)

A tester checks whether input fields properly sanitize special characters to prevent SQL Injection attacks.

Non-Functional Testing (Compatibility Testing)

A tester checks if the web application renders correctly and maintains its layout across Google Chrome, Safari, and Mozilla Firefox on both macOS and Windows.