Software Testing

SOFTWARE TESTING

• Is a Verification and Validation process (software program, application or product);
• Is a process os executing a program or application with the intent of finding the software bugs;
• Activity to check whether the actual results match the expected results and the ensure that the software system is defect free;
• Helps to identify errors, gaps or missing requirements

VERIFICATION

• Make sure the product behaves the way we want it to;
• Make sure that the product is designed to deliver all functionality to the customer;
• Is done at the starting os the development process

VALIDATION

• Is determining is the system complies with the requirements and performs functions for which it is intended and meets the organization's goals and needs;
• Done at the end of the development process and takes place after verifications are completed;

Slide 4

• NEEDS AND EXPECTATION OF CUSTOMER
• SPECIFICAtION
• PROCESS VERIFICATION VALIDATION
• PRODUCT

BASICS OF SOFTWARE TESTING

• Blackbox Testing (Functional Testing)
• A method of St that verifies the functionality of an application without having specific knowledge of the application's code/internal structure. Tests are based on requirements and functionality;
• Used for validation;
• QA team.
• Whitebox Testing (Structural Testing and Glass Box Testing)
• Is a testing technique that takes into account the internal mechanism os a system;
• Software developers.

TYPES OS TESTING

• Unit Testing
• Integration Testing
• Functional Testing
• System Testing
• Stress Testing
• Performance Testing
• Usability Testing
• Acceptance Testing
• Regression Testing
• Beta Testing

UNIT TESTING

• Whitebox testing;
• Is the testing of an individual unit or group of related units;
• Tests whether what is implemented producing expected output against given input.

INTEGRATION TESTING

• Whitebox testing and Blackbox testing;
• is testing in which a group of components is combined to produce output.;
• The interaction between software and hardware is tested.

FUNCTIONAL TESTING

• Blackbox testing;
• is the testing to ensure that the specified functionality required in the system requirements works.;

SYSTEM TESTING

• Black box testing.
• System testing is the testing to ensure that by putting the software in different environments (e.g., Operating Systems) it still works.
• System testing is done with full system implementation and environment.

Stress Testing

• It falls under the class of black box testing.
• Stress testing is the testing to evaluate how system behaves under unfavorable conditions.
• Testing is conducted at beyond limits of the specifications.

Performance Testing

• It falls under the class of black box testing.
• Performance testing is the testing to assess the speed and effectiveness of the system and to make sure it is generating results within a specified time as in performance requirements.

Usability Testing

• This falls under the class of black box testing.
• Usability testing is performed to the perspective of the client, to evaluate how the GUI is user-friendly?
• How easily can the client learn?
• After learning how to use, how proficiently can the client perform? How pleasing is it to use its design?

Acceptance Testing

• It falls under the class of black box testing.
• Acceptance testing is often done by the customer to ensure that the delivered product meets the requirements and works as the customer expected.

Regression Testing

• It falls under the class of black box testing.
• Regression testing is the testing after modification of a system, component, or a group of related units to ensure that the modification is working correctly and is not damaging or imposing other modules to produce unexpected results.

Beta Testing

• Beta testing is the testing which is done by end users, a team outside development, or publicly releasing full pre-version of the product which is known as beta version.
• The aim of beta testing is to cover unexpected errors. It falls under the class of black box testing.