Unit Testing:
Small pieces of codes may undergo this heading but those
should be typical, alone and isolated. If the test is using some external
resource like network or database, then it could not be treated as unit
testing. It should be fairly simple to write
that essentially gives the function that’s tested some inputs and then check
whether the function output is correct? Unit testing is great in preventing
regressions as well as bugs that occur repeatedly. It also plays a vital role
in making the good design of the prospective code.
Integration Testing:-
The name suggest, in integration testing the idea is to
test how parts of the system works together. These tests are similar to unit
test but unit test is isolated from other components but integration test doesn’t.
a unit test for database access code would not talk to a real database but an
integration test would be. When we have to test the two systems in separate i.e
the database and the app the integration testing will be carried out instead of
unit testing. Integration testing is slower than unit testing due to the added
complexity. It can be carried out by writing the same tools as in unit testing.
Functional Testing:-
Functional testing is also sometime called browser testing;
it is the test of complete functionality of any application. In practice with
web app, this means using some tools to automate a browser which is then used
to click around on the pages to test the application. Unit test may be used to
test the individual function and integration test to check the two or more
parts nicely but functional test is on the whole. Functional tests should be
used for testing common user interactions. If you would manually test a certain
flow of your app in a browser, such as registering an account, you could make
that into a functional test.
Blogger Comment
Facebook Comment