It saves lots of time and effort because Sanity testing is focused on one or few areas of functionality There is no effort put in towards it’s documentation because it’s usually unscripted It helps in identifying the dependent missing objects. It is used to verify that a small functionality of the application is still working … Read more
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 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
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
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
Software Testing has different goals and objectives.The major objectives of Software testing are as follows: Finding defects which may get created by the programmer while developing the software. Gaining confidence in and providing information about the level of quality. To prevent defects. To make sure that the end result meets the business and user requirements. To ensure that … Read more
A defect is an error or a bug, in the application which is created. A programmer while designing and building the software can make mistakes or error. These mistakes or errors mean that there are flaws in the software. These are called defects. When actual result deviates from the expected result while testing a software application … Read more
1. Walkthrough: It is not a formal process It is led by the authors Author guide the participants through the document according to his or her thought process to achieve a common understanding and to gather feedback. Useful for the people if they are not from the software discipline, who are not used to or cannot … Read more