Understanding The Difference Between Unit, Integration and Functional Testing

Week 9 Software Testing Blog

This week i have decided to read Understanding The Difference Between Unit, Integration and Functional Testing by Sushma S.
The article uses a login page as an example to help explain the difference between unit, integration, and functional testing. The reason for this is that a login page is extremely common and usually used in most web applications. It then goes over the cases for each type of testing and they are as follows:

Unit Testing –

Field  length for username and password

input field values should be valid

login button is enabled only after valid values are entered in both fields

Integration Testing –

user sees the welcome message after entering valid values and pushing the login button

users should be navigated to the welcome page or home page after valid entry and clicking login button

Functional Testing –

the expected behavior is checked

welcome message after succesfull login

can an inactivated user login

is there a forgot password link

Unit testing is generally done by the software developer who knows the code well. It is important for finding bugs early on in the development process, and is done before any integration or integration testing occurs. “Unit tests save time and cost, and it is reusable and easy to maintain”. After unit testing comes integration testing. After everything has been tested as a unit then integration testing occurs.
This when the units are put together and tested as a whole. This tests how the system works together and verifies that the behavior is correct. Then there is functional testing. This is a black box technique where the functionality of the system is tested. This basically means that we are testing that the behavior of the application and not the code itself. In order to successfully test an application you need to use all three testing methods. This provides the best test suite where any possible bugs should be found.

Here are some other links that i found usefulL:

https://blog.tentamen.eu/cleanup-order-in-selenium-headless-test/

http://www.softwaretestinghelp.com/how-perform-software-product-testing/

http://blog.smartbear.com/api-testing/top-5-api-testing-blog-posts-of-2016/

http://rhythmoftesting.blogspot.com/2016/12/thoughts-on-agile-testing-days-2016-pt-2.html

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s