Search Results

Some of the concerns we have are potential side effects of the smoke test run and interference with the active users during the run. … What are the general guidelines for running smoke tests against production and what issues can we expect to encounter? …

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

Just wanted to know the difference between Smoke Testing and Sanity Testing with software examples for better understanding. …

The QA manager in our organization is demanding that our dev team, which I am the manager of, do the smoke testing after we set up the testing environment and before the QA team begins testing, i.e. he …

I run automated smoke tests for my web application, but until now, these tests are not covering offline excel spreadsheets that are downloaded by the user. … I'm starting a study to find possible solutions to write in my script a way to let the user download and fill the spreadsheet through the smoke test. Has anyone already implemented this? …

I build a test automation framework with selenium for my large sitecore application. Everything was ok until the content editors started changing stuff around, item names and so on. … I kept updating my smoke test all over again and again! The Smoke test goes through the pages and checks if they are active, looks for some necessary details, footnotes, social tags and so on. …

Before actually starting testing we do smoke testing and after that we start the actual testing. … Can we take the results of the smoke testing session as pre-condition and assumption while writing test cases? If yes/no then why? …

When there is a new build we perform smoke testing,in few projects they call it as sanity testing. Can someone please elaborate on the difference between the both? …

For Smoke test this type need to run before we start any testing with build deployment and this test is just a "surface" level. But how about Sanity test? … And as my knowledge we should execute those tests in order like: Smoke -> Sanity -> Re-test -> Regression, is it right? …

let's say for the 1st time I have checked performed Smoke testing (application main feature) on the 1st day and then I report a Bug and developer fixed and deployed the app I test environment then do I … and let's say testing time is very less than do I have to do the sanity test+smoke testing again(for each bug i report)? …

Lets say we have 3 crucial features in each module, so we will execute 15 test cases in smoke test cycle. Right? We will not test these 15 features in deep. Right? … So can we have smoke test suite as a standard one for each sprint? Generally how long should be a smoke test cycle? Should it be short like 3-4 Hours? …

I want to apply smoke testing and sanity testing to running testing projects. So any one can help me by proper plan using which I can apply real smoke and sanity testing professionally as QA. …

Suppose I have five test cases out of which three are grouped in "Smoke Testing" and two have not been grouped at all. … @Test (priority=3, groups={"Smoke Testing"}) p v Test1(){} @Test (priority=1, groups={"Smoke Testing"}) p v Test2(){} @Test (priority=2, groups={"Smoke Testing"}) p v Test3(){} @Test (priority=5) p v Test4 …

Each test is different. Some are big and talk to databases, others quick and self contained. We all know we'd prefer the fastest and most robust test that does the job. …

Automated tests are divided into Smoke Test Suite folder and Regression Test Suite folder. I have created a simple "Test" script so it allows to me execute all automated test cases. … However I would like to know if there is a way of setting up the script configuration so when I type in console for example npm Test Smoke Suite or npm Test Regression Suite only of will be executed. …