Software Testing Tutorials

What is smoke testing?? Verifying the basic feature or critical feature in an application before going in-depth testing in a high-level manner is called as smoke testing. In smoke testing we provide only valid data and perform testing i.e we perform only positive testing. Smoke testing helps us to find out is the application capable enough to handle in-depth testing. It helps us to find out is the application testable. There are different name given to smoke testing like Sanity, Dry run, Initial build verification, etc Also Read : Acceptance Testing When we perform smoke testing?? As soon as we get the build we will start with smoke testing. Refer to the image below. As shown in the image above after white box testing is done smoke testing starts. So smoke testing is done after white box testing and then in-depth testing is done like functional testing, integration testing, etc. How to perform smoke testing??                       Let us take an example of the login page of a website.

System Testing : End to End testing where a testing environment is similar to a production environment. Testing environments are used by the tester where dummy transactions are carried out to check the quality of software. The production environment is used by the customer to carry out a real business transaction In system testing, we test complete and fully integrated systems. How to perform System Testing? Let us understand how to perform system testing with the example of an online transaction :                                                                                                    So as a tester following things will be tested in system testing : When User A Transfer balance to User B then after transferring the balance User A balance should be deducted from his Account and when user A checks his balance then available balance =Before transaction balance - transfer balance When User A transfers the balance to user B then we should check whether transfer entry is gettin

What is Integration testing? Testing the data flow between the two features or modules is called integration testing. Let us take an example of a banking application. So in the above image, there are two users (User A and User B) so in integration testing following thing will be tested: If user A transfers the balance to user B then that amount should be reflected in the user B account balance section. If user A transfers the balance to user B then that amount should be reflected in the user B statement section. If user A transfers the balance to user B then from user A account amount should get deducted and the updated amount should be visible in the balance section of user A account. If user A transfers the balance to user B then that debited amount should be reflected in user A statement. If User A does any bill payment then that bill payment amount should get debited from the balance section of user A account. If user A does bill payment then that bill payment transaction should ge