diff b/w smoke and sanity testing and what is migration
plan in testing?
Answer Posted / nitin sharma
Depends on Company to Company Smoke testing is done by build
release engineer before giving build to testing team,He will
check all the major functionality of product then Tester
will check again major functionalities before accepting the
build and if they found any problem in that then it will
reject and again send back to dev team.
| Is This Answer Correct ? | 3 Yes | 0 No |
Post New Answer View All Answers
What are the advantages of waterfall model?
Beyond the customary advantages of having a testing group, what are the benefits does a company receive from a well run, automated testing group?
Hi I want to start online training couses for testing Any body plz help me out how to start the online courses Plz post the answer here or send me a mail for kommineni.1020@gmail.com
To specify the test artifacts involved in testing.
Can anybody give me some tips on how to face telephonic interview and Write some expected telephonic questions as a 2+yr exp. in testing. Try to give Ques. that u already hv faced in telephone. Plz Help me out friends.
What is the difference between load testing and performace testing?
How can write testcases on a code under development pls give asnwer
how can you test the web environment for security testing?
In testing environment have you ever found any areas for improvement while you at work. (Please give some real life example).
What is sanity?
What is application programming interface (api)?
Hi ALl, Can you please list out Q & A for Test Lead,which Interviewer may ask in interview for Test Lead position
I know functional test cases are derived from frs and system design specs. But are test cases for performance, database, boundary, relational integrity and other types of tests other than functional tests created from frs and system design specs as well? When are these test cases created? Are they in the same test plans alongside functional test cases or is their a different test plan that includes these test cases?
What is error cusing tecnique
What is your approach when requirements change continuously?