1 / 1

What is Smoke Testing How to do with EXAMPLES

Smoke testing is performed when the softwareu2019s new functionalities are being developed and an existing build is being integrated with it. This will in turn verify whether the crucial functionalities are working correctly or not. Developers will make sure about the applicationu2019s correctness before releasing the build to the QA team.

Download Presentation

What is Smoke Testing How to do with EXAMPLES

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 is Smoke Testing? How to do with EXAMPLES Software defects can be effectively detected in the early stages of software development through the smoke testing process. In order to tackle with rapid release and build cycles, especially in an agile and DevOps environment, smoke testing can be an effective process to ascertain whether the changes made have introduced new defects, which, in turn, degrades the software integrity. This testing method can be performed in another context such as continuous integration also. In this article, you will get to know about smoke testing explained with a few examples. Smoke testing is performed when the software’s new functionalities are being developed and an existing build is being integrated with it. This will in turn verify whether the crucial functionalities are working correctly or not. Developers will make sure about the application’s correctness before releasing the build to the QA team. What is Smoke Testing? It is a testing method that verifies whether a deployed software build is stable or not. Defects are being found in software at a basic level of functionality. The evolution of test case libraries takes place over an extended period of time. A set of tests can be planned so that a given level of functional coverage can be achieved as there is enough time in the new system development. In order to build a complete and robust set of tests, a set of simple smoke tests is required. Example 1: Checking the login functionality: The specific ‘app’ is launched. Then the user goes to the ‘login page,’ enters the ‘credentials’ and clicks on the ‘Login’ button. If the user has provided the correct login details that means the login is successful and thus the “login functionality” is successful. Example 2: Checking the video launch functionality: First, Go to the ‘video’ page. The user clicks on the ‘video’ button and then the smooth playback of the video starts, but, the video player is not popping up. This means that the “video launch functionality” has failed and needs to be tested again, keeping in perspective what went wrong and then taking corrective measures. Example 3: For example, there is an e-commerce site and there are specific features that need to be tested and worked upon by the tester. Here, the function to place an order is tested. After testing, the tester must provide a detailed analysis of the application’s functionality. Following is the workflow: Click on the specific item The item’s description page will be opened Click on the ‘Add on Cart’ button The Add on cart page will open Click on the ‘Buy now’ button The payment options will be displayed from which the specific payment option can be selected by the user Finally, the order is placed successfully Example 4: When APIs are tested, basic defects may be the cause of the failures. When smoke tests are used in the early stages of development, the verification and validation of APIs take place so that solid integration is achieved. The functionality is validated by other smoke tests because of which the integration is not impacted by integration directly. Example 5: Adding functionality to items: The items are being added to the cart. A specific category is selected by the user from the list. The item is then placed in the shopping basket. Adding the product to the shopping cart. But, the item is not able to be added to the shopping basket. This means the functionality has failed and needs to be tested again. Example 6: Checking the sign-out functionality: The sign-out functionality is examined. The user will sign out by clicking on the ‘Sign out’ button. But, still, the user is unable to sign out. This means that the test has failed and the sign-out functionality needs to be tested again. CONCLUSION If you are looking forward to implementing smoke testing for your specific project, then do get connected with a globally renowned software testing services company that will provide you with a viable testing strategy that is in line with your project specific requirements. www.TestingXperts.com To know more about our services please email us at info@testingxperts.com USA | CANADA | UK | NETHERLANDS | SOUTH AFRICA | INDIA | SINGAPORE © 2022 TestingXperts, All Rights Reserved © www.testingxperts.com

More Related