Search Results

I am currently working on updating regression test suite. … Would these test be considered more as sanity tests or smoke tests? Thank you. …

In my field, Sanity Tests are designed as a checklist which include necessary functions somewhere between 60 ~ 70 test cases. … So if the new version passes Sanity Testing, we can start regression test cases. And smoke tests aren't managed by the QA Team. It is handle by Dev Team. …

In this case, "sanity test" and "smoke test" are interchangeable. Wikipedia acknowledges a relationship between these two terms as well (also on the "smoke testing (software)" page). … Since some organizations discourage using "sanity check" or "sanity test", "smoke test" would be the preferable term. …

This will help you to create use/test cases along with ways to find out how to break application. … You must be also clear with different types of testing such as Regression, Sanity, Smoke and also the testing processes that are followed in the project. …

You don't have to test the page title every time, but there are cases you do. People often test the page title as it acts like a smoke test. If it is wrong, you can fail the test and move on. … data in the saved variable In this case, since the page title changes based on user-created content, it's beneficial to test it! …

My manager assigned me to reduce the number of bugs in production and allocated a new dedicated smoke test team under me. my team need to perform system testing in every sprint and make customer reported …

I recommend at minimum a nightly run of test automation so that regression of existing tested features will be caught within a day of being introduced to the code. … If you can run an automated smoke test with every build of the software, so much the better. …

There is a smoke-test automation in place to verify the expected functionaly. …

Your smoke test automation should catch any critical functionality that's broken. …

Can someone guide us on whether we need to completely retest or if we can run smoke or sanity tests? …

When we receive a build of any web based or mobile based application we generally use this process: Smoke testing of the build :- Which consist a short positive flow of application. … Functional testing:- Which consist of all negative and positive testing using test cases. …

Start testing and test case creation ASAP as you get AC(before real implementation). … These features need to be tested once we have ensured that the application works in principle (the smoke test was successful). …

Regression Testing on Stage environment Smoke/Sanity Testing on Production environment. … Moreover, in case you have automation in your project than that can also be leveraged for executing Smoke/Sanity test executions. …

If agile is followed then creating test cases when feature development is in progress and executing those test cases when feature is deployed on QA instance will help in finding the bugs in early stage … Moreover, side by side Should I identify Automation test cases from the get go? Yes, if we have few test cases automated for smoke, sanity and regression then it will save time in regression phase. …

-Smoke tests: To ensure that the basic functionality of the product is working correctly. … An essential part of any test plan is the definition of a strategy for test automation. …