IF its is a interview question
Then add one more sentence to the above words
Its is basic testing. All the tester has first test or
checking the application orally that all the
functionalities are working properly or not.
Murali
murali.indrani@gmail.com
9942999500
chennai
A quick-and-dirty test that the major functions of a piece
of software work. Originated in the hardware testing
practice of turning on a new piece of hardware for the first
time and considering it a success if it does not catch on fire.
1. When testers receives an application (Build) then smoke
test is run to ascertain if the build is stable and it can
be considered for further testing.
OR
Smoke testing is cursory way of testing an application to
ensure that application is ready for major testing effort.
2. Smoke testing can be done for testing the stability of an
interim build.
ok suppose on hr application is there ok
in that so many minor functionalities are there but the
major functionalities are like
* name
* DOB.......
IF you wont enter any data in the mandatory field it has to
prompt an error message
and after filling all the mandatary fields then only the
save button should come to enable state
this is one of the major functionality in the application
so we will write test cases for all the functionalities
the particulat(above functionality) test case id is 100.
ok total 300 test cases are there
to execute all those it may take 1 month time.
if suppose you are execute the test cases in the 100th test
case when we click on save button the application crashes
so it is a show stopper
so what the tester will do is first he will check all the
functionalities with out executing all the testcases with
in 2 or 3 days if the build is acceptable testers will do
real testing otherwise we will reject the build.
if you have any doubts post me jyoshna_5785@yahoo.com
ok in
means
see we have to prepare test cases before getting the build
only
but we wont execute these test cases on the build while
doing smoke testing ok
for this you must have basic knowledge on the application
ya working as a test engineer
yes fastly we have to check all the major functionalities
not all the functionalities
dont ask me what are major functionalities
depends on the application we categorise the major
functionalities
When we get the build initial we perform smoke testing the
aim of this testing is to check basic functionality. Ex. by
giving URL home page should be open.It is wide approach.We
touch all the functions but not in depth. If smoke testing
fails we do not go for further testing.
Hey Mr. V,
Laxmi give u write answer. Then Why r u ask that Whether
he is working as a tester?
If u dont beleive in any person, then leave this forum, and
learn by yourself.
Just believe in others and share the knowledge.
Hi,
Smoke Testing means checking whether the main
functionalities of application are working properly or not.
Sanity Testing means checking whether the application is
accepting cusomer expected values or not.
Whenever the project is at maintenance phase the client
will be using his own data- is the same data given to the
test engineers or any other dummy data
Hey all,in a web applications,i am typing the URL in the
browser and entering the Username & password.After clicking
Login button,where the authentication will happen & how (i
mean how is the process goes on...browser,web server,DB
server level)...Pls answer...
winrunner q's..(if winrunner
1.explain types of recording modes?
2.how winrunner recognize GUI objects?
3.what is there in GUI map editor?
4.explain types of checkpoints?
5.syncronization point?
6.diff. between wait st. and synchornization?
7.diff.between is treturn & texit?
8.diff between tl_step and report_msg?
9.what is data driven test?
10how we parameterize the variable?
11.some ddt commands?
12.why we need to automate ?
13.explain database checkpoints with connectivity?
14.diff..between compiler module and main script?
15.expain in,out,inout parameters?
16.function generator?
17. Search path,breakpoints?
18.diff between step,step in,step out?
What should I do if the name of the field is change in new
version?How should I maintain it in Test Case Document?
Eg:
1)On Login Window:if Login button changed to Ok button
2)the Name of the Login Window get changed
3)Suppose New button adds to Login Window
4)Suppose For Login button there is Alt+L is used in new
version
Please tell me as early as possible
Thanks in advance!!!