SYSTEM TESTING

3) SYSTEM TESTING It is end-to-end testing wherein testing environment is similar to the production environment. Here, we navigate through all the features of the software and test if the end business / end feature works. We just test the end feature and don’t check for data flow or do functional testing and all. Let us consider an example to explain System Testing. Let us consider Citibank wants a software for overdraft feature....

Read More

INTEGRATION TESTING

2) INTEGRATION  TESTING Testing the data flow or interface between two features is known as integration testing. Now let us consider the example of banking s/w as shown in the figure above ( amount transfer ). Scenario 1 – Login as A to amount transfer – send 100rs amount – message should be displayed saying ‘amount transfer successful’ – now logout as A and login as B – go to amount balance and check balance – balance is increased...

Read More

BLACK BOX TESTING

It is verifying the functionality ( behavior ) against requirement specifications. Types of Black Box Testing 1) FUNCTIONAL TESTING Also called component testing. Testing each and every component thoroughly (rigorously) against requirement specifications is known as functional testing. For ex, let us consider that Citibank wants a s/w for banking purpose and it asks the company Iflex to develop this s/w. The s/w is something as shown...

Read More

WHITE BOX TESTING (WBT)

Entire WBT is done by developers. It is the testing of each and every line of code in the program. Developers do WBT, sends the s/w to testing team. The testing team does black box testing and checks the s/w against requirements and finds any defects and sends it to the developer. The developers fixes the defect and does WBT and sends it to the testing team. Fixing defect means the defect is removed and the feature is working fine. Test engineers...

Read More