Functional Testing

Functional Testing is a Quality Assurance process in which, QA team provide the input to the function and check the output without checking the internal structure of the function. This is a Black Box Testing. In the Function Testing, Test team provide the input and check the output to validate that whether the output matching with the expected output.



In Functional Testing, test team verify the functionality with the Business Requirement. This testing is perform with the client specification and design document that prepared in early process.

In Functional Testing, we check that each component of the software working as expected in Specification.

Functional Testing may be positive and Negative. In Positive Functional Testing, Test Team provide the valid input to check the output while in Negative Function Testing, Test Team provide the Invalid input to check the output. 

Functional Testing involve following steps:

• Understand the component on which Test will be executed
• Create Input Data( Valid or Invalid)
• Focus on output to validate it with expected result
• Execute the Test case
• validate output with expected result

Type of Functional Testing

• Smoke Testing: In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.

• Sanity Testing: Sanity Testing is perform when QA team received the build after fixes of minor bugs or some new functionality added. In Sanity Testing, QA team check that the bugs that generated in last build should be fix and due to those bug fixes there should be no new bugs generated. So in Sanity Testing first QA team check the regression testing and after regression testing QA team verify the previous bugs.

• Regression Testing: When developer assign a new built for the QA team to test and QA team find some bugs in that build they assigned those bugs to the Dev Team to fix. Developer team fixes those bugs and assigned back for the QA team to test. Now QA team will verify the new build to check weather assigned bugs fixes or not and QA team need to validate the related areas of assigned bugs to verify that weather all previous functionality is working fine due to changes done on the software build.  In terms of definition Regression Testing is the type of testing which cover to verify the working functionality (functional and Non functional) that can be changed or wrongly working after enhancement and bug fixes.This is the Verification Method.

• Unit Testing: Unit Testing is the smallest testable part of the software.  It may be a function, Class, procedure and the Interface. In Unit Testing individual unit of source code are tested to determine whether they are fit for use.

• Integration Testing: When all small unit of code combined together or we can say integrate together then perform the testing between the interface of these units to verify that are these unit working fine when these are combined. Integration Testing occur after Unit Testing. In Unit Testing , developer concern only over the each module and fixes all error in that but developer not focused that what is the effect of bug fixes in other modules. Each Unit is developed by different different programmers so in Integration Testing, We will test the data communication between these Units.

• White Box Testing: Another name of this testing is Glass Box Testing. Like s transparent glass everything is visible inside the glass. Just like in this type of Testing, Testing team need to know about the internal structure and code of the Software. Testing are based on the Code coverage, Branch coverage, Path coverage.

• Black Box Testing: In this type of Testing, Testing team need not to be aware regarding the internal structure of the software. Testing Team do not need any knowledge regarding the code to perform this type of Testing. Testing team just focus on the requirement and the functionality. Testing team just focus over the actual result and matching that result with the expected result.

• User Acceptance Testing: Acceptance Testing is the formal testing as per the user needs, requirement and the business requirement to determine whether system satisfies the acceptance criteria and enable the user or customer to determine weather to accept the system or not.