Skip to main content

What Is Functional Testing Explain It with Example?

Functional testing means testing the application against business requirements. Functional testing is executed using the functional specifications given by the client or by the design specifications according to use cases given by the design team. Role of functional testing is to validating the behavior of an application.

Functional testing is more important because it always verifies that your system is fixed for release. The functional tests define your working system in a useful manner. In functional testing tester has to validate the application to see that all specified requirements of the client whatever we have said in SRS or BRS have been incorporated or not.

Functional testing is always concentrating on customer requirements and whereas the Non-Functional testing is always concentrating on customer expectations.

Functional and Non Functional Test Cases

Functional test cases target business goals and non functional test cases target performance, resource utilization, usability, compatibility etc. Functional testing is a part of system testing.

Example of functional testing is explained below


Considering example if you are functionally testing a word processing application, a partial list of checks you would perform minimally includes creating, saving, editing, spell checking and printing documents.



Types of Functional Testing


Functional testing falls in to two categories:

1. Positive functional testing: - This testing carry exercising the application’s functions with valid input and also verifying that the outputs are correct.

Example:-

Again continuing with the word processing example, a positive test for the printing function might be to print a document containing both text as well as graphics to a printer that is online, filled with paper and for which the correct drivers are installed.

2. Negative functional testing: - This testing involves exercising application functionality using a combination of invalid inputs, some unexpected operating conditions and by some other “out-of-bounds” scenarios.

Example:-

Again continuing with the word processing example, a negative test for the printing function might be to disconnect the printer from the computers while a document is printing.

What probably should happen in these scenarios are a plain-English error message displayed, informing the user what happened and instructing him/her on how to fix the problem.

Conclusion:
At last we conclude that in functional testing functionality of the module is tested and structure is not considered. It is performed, based on user's perspective. These tests ensure that the system does what users are expecting it to do.

This type of testing means testing the functionality example include input the proper data and checking the output as per the requirement documents.

Comments

  1. Great Wonderful Answer!!

    ReplyDelete
  2. This was wonderful explanation! thank you

    ReplyDelete
  3. Explanation was good and i need some more examples

    ReplyDelete
  4. very nicely explained, thank you!

    ReplyDelete
  5. So apparently it it's not testing a specific function? All this time I've not been applying to certain jobs thinking I didn't qualify... :)

    ReplyDelete
  6. Good for a KG kid.. Love it..

    ReplyDelete
  7. thankyou sir... very nice... :)

    ReplyDelete
  8. Explanation was good............thank you

    ReplyDelete
  9. Thanks for sharing..:-)

    ReplyDelete
  10. it ws good explanation but still need more example.....

    ReplyDelete
  11. Thank u for sharing. Simple and clear language :)

    ReplyDelete
  12. Thank you for wonderful explanation.
    But I have a doubt, What type of risks or issues can be in functional testing?

    ReplyDelete
  13. functional testing should ensure software application/product quality by providing measures for the following factors:

    Correctness
    Reliability
    Usability
    Integrity
    Conformity

    ReplyDelete
  14. This is really helpful concise and informative.

    ReplyDelete
  15. Awesome explanation very simple way thanks

    ReplyDelete
  16. nice explanation
    but i need some more
    1.when we go for functional testing ?
    2.why functional testing required ?

    ReplyDelete
  17. Dear nandita...It is purely based on customer requirements. .

    ReplyDelete
  18. Awesome explanation...... thanks for providing & please keep going.....

    ReplyDelete
  19. Awesome explanation very simple way thanks

    ReplyDelete
  20. very explanations sir .....Myself Tamilmaran software manual tester IT Aerospace

    ReplyDelete
  21. very nice... good explanation :)

    ReplyDelete

Post a Comment

Popular posts from this blog

Difference Between Verification And Validation With Example?

Verification and Validation example is also given just below to this table.                Verification               Validation 1. Verification is a static practice of verifying documents, design, code and program. 1. Validation is a dynamic mechanism of validating and testing the actual product. 2. It does not involve executing the code. 2. It always involves executing the code. 3. It is human based checking of documents and files. 3. It is computer based execution of program. 4.  Verification uses methods like inspections, reviews, walkthroughs, and Desk-checking etc. 4.  Validation uses methods like black box (functional)  testing, gray box testing, and white box (structural) testing etc. 5.  Verification  is to check whether the softwar...

Regression Testing with Example and Strategies

Regression Testing is done to ensure that fixed bug does not affect the remaining functionality of the modules and also the functionality of the same module. In short you can say regression testing  is always done to verify that modified code does not break the existing functionality of the application and works within the requirements of the system. Regression Testing Example  For Example there are three Modules in the Project named Admin Module, Personal Information, and Employment Module and suppose bug occurs in the Admin Module like on Admin Module existing User is not able to login with valid login credentials so this is the bug.  Now Testing team sends the above - mentioned Bug to the Development team to fix it and when development team fixes the Bug and hand over to Testing team than testing team checks that fixed bug does not affect the remaining functionality of the other modules (Admin, PI, Employment) and also the functionality of ...