1 / 1

What happens if Smoke Testing is not taken up

The software build cannot be qualified for further rounds of testing. Early major issues cannot be detected quickly and that too in a cost-effective manner. Conformance to requirements and system stability cannot be demonstrated in the absence of smoke tests. In order to implement one or more product functions, a build is required, which basically includes engineered components, reusable modules, libraries and data files. <br>

Download Presentation

What happens if Smoke Testing is not taken up

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. WHAT HAPPENS IF SMOKE TESTING IS NOT TAKEN UP? If smoke testing is not performed, then the working of the build cannot be optimized, which may in turn cause issues in the software development process in terms of functionality and performance. For this particular reason, it is known as “Build Verification testing.” The working of the basic functionalities of the application cannot be properly assessed if smoke tests are not performed. Following are a few key points that depict as to what happens if smoke testing is not taken up: ·The issues that got introduced by integrating components cannot be identified ·The issues that have been fixed in the previous build cannot be verified and hence the major functionalities of the application are impacted or cannot be ascertained ·The showstoppers in the build cannot be identified ·The detection and correction of major defects cannot be simplified ·The major severity defects cannot be found ·The defects in the application functionality that may have been triggered by the new code cannot be identified ·The quality of the system cannot be improved and subsequent risks cannot be reduced ·Crucial errors cannot be detected and thus cannot be corrected either ·It will be difficult to access the progress and integration risks also cannot be minimized ·The outcome of software’s new functionalities that are developed and integrated with an existing build cannot be analyzed and ascertained. https://www.testingxperts.com/

More Related