Sanity testing is usually performed when any minor bug is fixed or when there is a small change in the functionality. It is a kind of software testing which is done by the testers to ensure that the functionality is working as expected. Sanity testing is narrow and deep. Unlike Smoke testing, Sanity testing is focused on one or two … Read more
Smoke testing does not cover the detailed testing. It’s a non-exhaustive testing with small number of test cases because of which we not are able to find the other critical issues.
It helps in finding the bugs in the early stage of testing. It helps in finding the issues that got introduced by the integration of components. It helps in verifying the issues fixed in the previous build are NOT impacting the major functionalities of the application. Very limited number of test cases is required to … Read more
Smoke testing is a type of software testing which ensures that the major functionalities of the application are working fine. This testing is also known as ‘Build Verification testing’. It is a non-exhaustive testing with very limited test cases to ensure that the important features are working fine and we are good to proceed with the detailed testing. … Read more
There are seven principles of software testing. They are as follows: 1) Testing shows presence of defects: Testing can show the defects are present, but cannot prove that there are no defects. Even after testing the application or product thoroughly we cannot say that the product is 100% defect free. Testing always reduces the number of undiscovered defects remaining in … Read more
The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect. For example if error is found in the requirement specifications during requirements gathering and analysis, then it is somewhat cheap to fix it. The correction to the requirement specification … Read more
There are two key things in defects of the software testing. They are: 1) Severity 2) Priority 1) Severity: It is the extent to which the defect can affect the software. In other words it defines the impact that a given defect has on the system. For example: If an application or web page crashes when a remote link is … Read more
Defect life cycle is a cycle which a defect goes through during its lifetime. It starts when defect is found and ends when a defect is closed, after ensuring it’s not reproduced. Defect life cycle is related to the bug found during testing. The defect life cycle can vary from organization to organization and also from project to … Read more
The cost of defects can be measured by the impact of the defects and when we find them. Earlier the defect is found lesser is the cost of defect. For example if error is found in the requirement specifications during requirements gathering and analysis, then it is somewhat cheap to fix it. The correction to the requirement specification … Read more
If under certain environment and situation defects in the application or product get executed then the system will produce the wrong results causing a failure. Not all defects result in failures, some may stay inactive in the code and we may never notice them. Example: Defects in dead code will never result in failures. It is not … Read more