[ACCEPTED]-What is functional testing?-terminology

Another way of thinking is this:

Unit Test:
Test 11 your code as units, calling methods and 10 verifying return values and object property 9 states/values

Functional Testing:
Testing 8 your code paths while preforming a task. This 7 ensures your application does what your 6 code says it does.

Integral Testing? Do 5 you mean Integration Testing?

Integration 4 Testing:
Testing your code by plugging it 3 into a larger mass to ensure you haven't 2 broken existing logic and you are able to 1 integrate back into the main branch.

Functional testing is making sure that customer 26 requirements are implemented in the final 25 product as specified in the spec. Unit testing 24 is to check that small portions of code 23 behave as intended. Integration testing 22 is making sure that the system is stable 21 when you combine all the different parts/modules 20 together.

For example, BigBank Corporation 19 wants a software that generates customer 18 bank statements and inserts 3 random fees 17 each month for each customer.

The Program 16 Manager writes the software functional specification 15 after several discussions with BigBank's 14 representatives.

A developer writes a module 13 that fills up a template statement from 12 a database. He performs unit testing to 11 check that most cases are covered (typical 10 customer, no data for the month, etc.)

Another 9 developer creates a random number generator 8 module. He performs unit testing on that.

The 7 integrator takes the two modules, compiles 6 them and performs integration testing to 5 ensure that they work well together.

Finally, in 4 order to deliver a beta version for BigBank 3 to try, the Test team performs functional 2 testing to validate that the software complies 1 with the functional specs.

Functional testing of the target-of-test 17 should focus on any requirements for test 16 that can be traced directly to functional 15 specifications or business rules. The goals 14 of these tests are to verify proper data 13 acceptance, processing, and retrieval. It 12 tests the features and operational behavior 11 of a product to ensure they correspond to 10 its specifications, and incorporates tests 9 that ignore the internal mechanism of a 8 system or component and focus solely on 7 the outputs generated in response to selected 6 inputs and execution conditions. This type 5 of testing is based upon typically black-box 4 techniques, that is, verifying the application 3 (and its internal processes) by interacting 2 with the application via the UI (User Interface) and 1 analyzing the output (results).

Source:http://softwareqatestings.com/introduction-to-software-testing/basic-steps-of-functional-testing.html

• Unit testing is within single application tier (presentation, business 5 logic, data access, etc.).

• Functional testing is across multiple 4 application tiers so that tests span pieces 3 of complete application functionality.

• Integration testing would 2 be tests across multiple application components 1 or even applications.

Unit Test: Test the smallest units of code 25 possible, usually one function or method. By 24 using mocks etc. this ideally should be 23 very fast and not hit the hard disk or network 22 in any way.

Functional Testing: Test a set 21 of functions/methods working together. Ideally, this 20 should also not go to disk or network as 19 well, but often will.

Integration Testing: Test 18 that run in the real world, going to real 17 (although test) databases, writes to disk, etc. You 16 are testing that your program works correctly 15 with other services, that it 'integrates' with 14 them correctly. You often will have a separate 13 program (ex. Selenium) that exercises the 12 tests, just like a real user would.

Also: White 11 Box Testing: Tests that know the internals 10 of how the program works. Unit tests and 9 Functional tests are often white box. An 8 example would be calling a function to save 7 a value and then checking the value in the 6 database for correctness.

Black Box Testing: Tests 5 that are ignorant of the internals and treat 4 the program/function/method as a "black 3 box". An example would be calling a function 2 to save a value and calling another (public) function 1 to get that value.

Functional Testing is these days is commonly 6 known as the End-to-End testing or System 5 testing if you look at the V-Model.

Unit 4 testing obviously testing the smallest unit 3 of code that is possible and integration 2 testing is checking that your units integrate 1 well with other parts of the system.

The term "functional testing" is commonly 17 applied to testing a system as a whole, e.g. a 16 web application from the browser end through 15 to the database layer. While I am guilty 14 of abusing this term myself, I believe the 13 terms "system testing" or "end-to-end testing" describe 12 it much better.

The other meaning of "functional 11 testing" can be just "testing functionality", which 10 is usually true for unit or integration 9 testing, too. But there are tests which 8 are not functional tests. Pretty much anything 7 that is regarding non-functional requirements 6 falls into that category, such as load testing 5 or profiling.

I think originally the distinction 4 might have been between "functional system 3 testing" and "non-functional system testing", nowadays 2 "functional testing" is often used to distinguish 1 end-to-end testing from testing subsystems/units.

First we should understand what is a 'function' with 15 respect to software?

Function can be considered 14 as a task/activity which is intended to 13 do by the software.

So, testing each and 12 every function of the software is called 11 functional testing

Coming to the unit testing 10 you will isolate the code and test each 9 unit of it.

Consider a method/function in 8 a program as an unit where you will pass 7 some parameters and expect the code to give 6 required output and testing such units of 5 code is called a unit testing

A collection 4 of units acts as a function of a software 3 and testing of such functions can be called 2 as functional testing

Please go through the 1 links to understand it better

http://www.guru99.com/unit-testing-guide.html

http://www.guru99.com/functional-testing.html