Explain Seven Testing Principles

Being a Software Tester, we have to aware about Testing principles. Let's explain Seven testing principles below here:- 1. Testing shows presence of defects:- Testing never proves that there are no defects in the application. It only can show that defects are present in the application. Testing mitigates the probability of undiscovered defects existing in an application or in the software. Although, even if no defects are found in the software,...

Read More

Explain Build Verification Testing (BVT)?

Build Verification Testing (BVT) :- A build verification (BVT) test is a set of tests run on each new build of a product or software to verify that the build is testable, before sending it to the testing team. It is generally a short set of tests which exercise the mainstream functionality of the application. Any build that fails the build verification test is rejected, and testing continues on the previous build of the product, provided there...

Read More

What is Black Box Testing? Advantages and Disadvantages of BBT.

Black Box Testing:- Black box testing is an approach where a tester test an application or a software without knowing the internal working of the Application Under Test (AUT). Black box testing is also referred to as functional testing, behavioral testing or input/output driven testing technique. For example:- when this approach (black box) are applied on an application or a software, the tester only knows the inputs and what the expected...

Read More

What is Retesting or Confirmation Testing?

Retesting or Confirmation Testing:- Retesting is done by the tester to ensure that the defects reported in the previous build has been fixed. In Retesting, tester re-run the failed test cases. Lets consider a scenario where a build is found to have 15 defects, which are then assigned to the developers for fixing. Once all these defects or bugs are fixed by the developers, the build is retested to verify whether the defects or bugs have...

Read More

Difference between Smoke Testing and Sanity Testing?

Difference between Smoke and Sanity Testing? Smoke Testing :- Smoke Testing is a wide and shallow approach. It means we (Developer) test an application in a cursory way without going into too deep. Smoke Testing is basically performs to test the health of builds before handed over to the testing team for deep testing. It is done by developer. Some times it is also done by testers too. Smoke testing is scripted i.e. either we use test cases or...

Read More