How we do the smoke testing?
- 12 Answers
- 15620 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / anitha
Smoke test is to make sure the Basic functionality of the
application is working fine or not.For example yahoo mail
if we enter login name , Password it should go to Inbox
page.This is the Basic function behind that.
| Is This Answer Correct ? | 10 Yes | 0 No |
Smoke testing will be conducted to ensure whether the most
crucial functions of a software work, but not bothering
with finer details.
Smoke Testing is conducted by testing team on receiving of
each build as to check whether build/release given is
stable and it can be considered for further testing.
| Is This Answer Correct ? | 5 Yes | 0 No |
Answer / hanumantha rao. k
Smoke Testing means, after receiving initial build, on that
build we able to check the MAIN FUNCTIONALITY on that
build, whether that functionality is existing or not is
called as Smoke Testing
| Is This Answer Correct ? | 1 Yes | 0 No |
as far as I know ...whenever QA tester receives a new
build, we will check the configurations of the application
(like database connections, printer and other technologies
connected to the application) and not related to
functionality.
Sanity testing is to check the major functionality of the
application(or build)
| Is This Answer Correct ? | 2 Yes | 2 No |
Answer / baskar palani
Smoke Testing:
Once new build of the application reaches the testing team,
will test the few major functionality of the system to
ensure whether the system is stable and agree to allow for
testing the remaining functionality of the system. These
kinds of testing will be done by one or two tester for min
30 minutes to 1 hrs.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / bhushan
Every one ans. here for Why we do the smoke testing ?
no body Ans. How ?? AND also
In interview they ask me following que.
what exactly mean Stability of System ???
please Clarify ?
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / smita
Smoke Test:
When a build is received, a smoke test is run to ascertain
if the build is stable and it can be considered for further
testing.
Smoke testing can be done for testing the stability of any
interim build.
Sanity testing:
Once a new build is obtained with minor revisions, instead
of doing a through regression, a sanity is performed so as
to ascertain the build has indeed rectified the issues and
no further issue has been introduced by the fixes.
Its generally a subset of regression testing and a group of
test cases are executed that are related with the changes
made to the app.
| Is This Answer Correct ? | 0 Yes | 0 No |
Answer / sumit
According to my views, both sanity and smoke are preliminary stage of testing before proceeding for full blown testing of a particular release or build of an application.
Sanity testing: Ensures that whether the basic supported features of an existing application is working and not affected with new changes.
Smoke Testing: This can be describe as let's say there are 10 new features introduced in a build or release, so in order to test each 10 features to finer level requires initial stage to be passed.
E.g. In a new feature there are some more search criteria added to an existing search page:
In sanity testing tester would ensure that search with any of the existing field is working
And In smoke testing tester would feed correct expected data in newly added field and perform search to make sure that correct result appears and if correct results not appears then testing of that feature can be stopped and appropriate action can be taken.
| Is This Answer Correct ? | 0 Yes | 0 No |
Hi Kiran,
Smoke testing is done when we receive the new
build not before the release. This is done to check the
stability of the application and to find if there are any
broken links in the application. This is done by checking
the links and some random check on the application
| Is This Answer Correct ? | 0 Yes | 1 No |
Answer / srinivas
Smoke testing is nothing but testing the application to
verify that it is stable r not.
In smoke testing we check the various connections like
database, printer, etc..
| Is This Answer Correct ? | 0 Yes | 1 No |
what would be purpose of Dashboard on Quality center? please provide me the advantage of dashboard? thanks in advance….
After you have completed the first phase of running the 'Test Cases' in TD, now that you have set the status of each step as Pass/Fail. How will you run the same 'Test Cases' for regression testing (say for 2rd or 3th build)?
I am using Quality Center 9.2. While raising a defect i can see that there is only option to send a mail to assigned and it is also sent to me. Is there any way i can send the mail to multiple users ? I know i can save the defect and than later sent it to multiple users, but is there any way where i can send it at the time of raising the defect itself. Any configuration that can be done by an adminstrator?
How to use testdirect like a dashboard?
how do we find that there are duplicate bugs in Test Director or quality center?
How many Test Managers in Test Director? Skjha2000@rediffmail.com
Hi All, Im currently getting to grips with the Document Generator in Test Director and have a query. We use TD to link requirements to test cases and I am attempting to produce a report which lists the requirement and the test case it is linked to. I cant see a way to do this as the test case link info resides on the Coverage page and it appears the only field available to display for requirements reports within document generator as those on the 'details' tab. Any tips?
What are the MIC& Reporter Class in DP?
How do you create Test script from Quality centre Using QTP
Which tool would be best for automation of DotNet?
Can any one tell how to install the TD in our system?
Explain about user authentication in TD related to OS?
WinRunner 
