day before yesterday i faced this question in value labs ,,,,
1.what is the exact difference between sanity and smoke
testing which will do first and say some sanity test cases.....
2. difference between UI,GUI & Usability testing and can i
access the form without testing GUI and how the blind people
can identify GUI of the form.....
anyone plzzz answer 2 me thanks in advance byeeeeeeeee
Answers were Sorted based on User's Feedback
Hey Mona
I am sorry to say but your answer is wrong. As I mentioned
in my earlier post smoke testing is done immediately after
build is received from development team to check the
stability of the build. Stability means to check whetehr
all the forms, buttons, links, etc are working. once it is
done we go for sanity testing i.e to check complete
functionalities of the module as per the requirement
mentoned in the SRS and we execute our test cases.
Thanks
Kishore
kishoresharma1@gmail.com
Is This Answer Correct ? | 10 Yes | 0 No |
Answer / aaditya
first we will smoke testing and after that sanity testing
is done.
Smoke testing:in this we check only that bild is uploaded
or not.
sanity testing:we also do functional testing.
Is This Answer Correct ? | 1 Yes | 0 No |
Answer / suvendu acharya
1.In Sanity testing we r just checking the look & fill of
the GUI according to the client specification or according
to the mockup screen.
In sanity testing we r not checkin any business logics not
the flow, we r just checkin the look & fill.
EX: Take the yahoomail login page, there is a logo in top
middle of the page, in right pane there r 2text boxes are
there, one check boxis there and one login button is there.
in sanity check we will check wheather all these fields r
there or not.according to client spec. doc the text colour,
the text size & the text style is ok or not we will check.
But in smoke testing we r checking all the functionalities,
wheather the application is working fine or not.
smoke testing is an adhoc type testing.
2.Sorry I dont know how the blind people
can identify GUI of the form.
Is This Answer Correct ? | 2 Yes | 4 No |
Answer / vikky
Hi Mona
You are right. I am agree with your answer. I have appeared
in interview in Fareportal, Gurgaon. The test lead asked
the diff. between smoke & sanity testing. Later he told me
that both are the same thing and it varies company to
company.
Is This Answer Correct ? | 0 Yes | 3 No |
Answer / mona
Smoke and Sanity testing are the same. To test that the
build is migrated successfully and all the needed code is
migrated successfully. This is followed by system testing.
Is This Answer Correct ? | 0 Yes | 5 No |
Plz explan entry and exit criteria with example??? thanks
hai friends, I need clarifications for some doubts in testing terminology. 1.What is thread testing. 2.What is bucket testing and which automated tool is used to do this test. 3. ERP testin automation testing. 4.What is Data Warehousing testing? 5.What is Implementation testing? 6.What is Shake out testing? please let me have the clarifications in detail
What is Test Design?
what is role of the tester in an organaisation and project? what is the daily work of tester?
How do you perform regression testing?
What is the type of the testing to check the availability of a website 24 * 7?
The applications are invited from the students between 18 and 23 years old. The age relaxation for reserved category students is 5years.so what are the test cases posible to write
Diff between ALM &QC?
How we test an ERP products? and wat approach we will fallows and wat r the tools avaliable for ERP testing?
Hi, Can anyone suggest a test case writing technique for the below scenario. 1. User draws a lines on the image 2. User selects the lines and right clicks ( Measuremnts like distance between the start and the end point, coordinates of start point and coordinates of end point) 3. User selects one of the measurement Measurement is displayed Just want to highlight, i am looking for a test case writing technique for above scenario.
what is a bad defect and why do we write bad defects?
list of methods that is used to document the requirements of a software.