Advanced Manual Testing Explained: Free Course Part 4

EXPLAIN FUNCTIONAL TESTING ?

• Functional Testing is type of software testing which validates the software system against the functional requirements/specifications. The purpose of Functional tests is to test each function of the software application, by providing appropriate input, and verifying the output against the Functional requirements.

EXPLAIN INTEGRATION TESTING ?

• Integration Testing is defined as a kind of testing where software modules are integrated logically and tested as a group. A typical software project consists of multiple software modules, coded by different programmers(developers). The aim of this level of testing is to expose defects in the interaction between these software modules when they are integrated

TYPES OF INTEGRATION TESTING

• INCREMENTALL INTEGRATION TESTING
• NONINCREMENTAL INTEGRATION TESTING

TYPES OF INCREMENTAL INTEGRATION TESTING

• TopDown Incremental Integration Testing
• Bottom-Up Incremental Integration Testing

Top-down integration testing:

• It is a technique is to simulate the behavior of the lower-level modules that are not yet integrated. In this integration testing, testing takes place from top to bottom. At First, high-level modules are tested, then low-level modules and then finally integrate the lower-level modules to high level to ensure the system is working asdesired.

Bottom-Up Integration Testing:

• In the bottom-up testing, each module at lower levels is tested with higher modules until all the modules are tested. The main purpose of this integration testing is, each subsystem is to test the interfaces among various modules making up subsystem. This kind of integration testing uses test drivers to drive and pass appropriate data to the lower-level modules.

Mixed / Hybrid Integration Testing –

• Mixed /Hybrid integration testing is also called sandwiched integration testing. A hybrid integration testing follows a combination of top-down and bottom-up testing approaches. The top-down approach, testing can start only after the toplevel have been coded and unit tested. The In bottom-up approach, testing can start only after bottom-level modules are ready. Mixed integration testing is also called sandwiched integration testing.

NON-INCREMENTAL INTEGRATION TESTING/BIG BANG APPROACH

            Whenever the relationship between the modules is not clear, non-incrementalintegration testing or big bang integration is executed. In this case the data is created in one module and is combined with all the other modules to perform testing. Check as well as test the flow of data between them. It is because of this that non-incremental integration testing is also known as Big Bang Integration. In this kind of integration testing approach, most of the developed modules are coupled together to form a complete software system (a major part of the system) which is then used for integration testing. This method is effective in saving time in integration testing process. However, if the test cases and their results are notproperly recorded, the entire integration process will be complicated and may prevent the testing team in getting their targeted goals or results of integration testing.

ADVANTAGES

• Helps testers in saving integration testing time.
• Here all components of the software are integrated at once.
• Convenient for small systems.

EXPLAIN SYSTEM TESTING ?

            SYSTEM TESTING is a level of testing that validates the complete and fully integrated software product. The purpose of a system test is to evaluate the endto-end system specifications. Usually, the software is only one element of a larger computer-based system. Ultimately, the software is interfaced with other software/hardware systems. System Testing is actually a series of different tests whose sole purpose is to exercise the full computer-based system. 

System Testing is carried out on the whole system in the context of either system requirement specifications or functional requirement specifications or in both the context. System testing tests the design and behavior of the system and also the expectations of the customer. It is performed to test the system beyond the bounds mentioned in the software requirements specification

EXPLAIN USER ACCEPTANCE TESTING

Acceptance testing, is a testing technique performed to determine whether or not the software system has met required specifications. The main purpose of this test is to evaluate the system's compliance with the business requirements and verify if it is having met the required criteria for delivery to end-users User Acceptance Testing (UAT) is a kind of testing performed by the end-user or the client to accept the software system before moving the software application to the production environment. UAT is done in the final phase of testing after functional, integration and system testing is done.

Who Performs UAT?

• Client
• End users

TYPES OF ACCEPTANCE TESTING

Alpha Testing:

Alpha testing is mainly used to determine the product in the development testing environment by a specialized team of testers usually called alpha testers.

Beta Testing:

Beta testing is used to assess the product by exposing it to the real end-users, usually called beta testers in their environment. Feedback is collected from the users and the defects are fixed. Also, this helps in enhancing the product to give a rich user experience.

What is Adhoc testing?

Adhoc Testing is an informal or unstructured software testing type that aims to break the testing process in order to find possible defects or errors at an early possible stage. Ad hoc testing is done randomly and it is usually an unplanned activity that does not follow any documentation and test design techniques to create test cases.

What is Re-Testing?

• Re-testing the application means verifying whether the defects have been fixed or not.

What is Regression Testing?

• Verifying an existing functional and non-functional area after making changes to the part of a software or addition of new features is termed so.

What is Recovery Testing?

• Checking whether the system is able to handle some unexpected or unpredictable situations is called Recovery Testing.

What is Installation Testing?

• Checking whether we are able to install software successfully (or) not, as per theguidelines given in the installation document is called Installation Testing.

-: THANK YOU :-