Answer Posted / 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 |
Post New Answer View All Answers
How do you ensure that there are no duplication of bugs in Test Director?
how do u call data file and gui file in testdirector
what are the type of testing and methodologies
What r the mandatory fields in TD?
What is the use of test lab in test director?
How can we export multiple test cases from td in a single go?
Is there any possibility to restrict duplication of defects being created in td?
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?
Can you please explain the procedure of connecting testdirector in qtp?
What is the Change management ?
What is Business Process?
What is architecture?
How can we split the tests in Test Director?
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 is Test Director's API execution tool(VAPI)?