Answer Posted / sudha

• A sanity test is a narrow regression test that
focuses on one or a few areas of functionality. Sanity
testing is usually narrow and deep.
• A sanity test is usually unscripted.
• A Sanity test is used to determine a small section
of the application is still working after a minor change.
• Sanity testing is a cursory testing, it is
performed whenever a cursory testing is sufficient to prove
the application is functioning according to specifications.
This level of testing is a subset of regression testing.
• Sanity testing is to verify whether requirements
are met or not, checking all features breadth-first.


• Smoke testing 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 fire and smoke. In software industry, smoke testing
is a shallow and wide approach whereby all areas of the
application without getting into too deep, is tested.
• A smoke test is scripted, either using a written
set of tests or an automated test
• A Smoke test is designed to touch every part of the
application in a cursory way. It’s shallow and wide.
• Smoke testing is conducted to ensure whether the
most crucial functions of a program are working, but not
bothering with finer details. (Such as build verification).
• Smoke testing is normal health check up to a build
of an application before taking it to testing in depth.

if yahoo ceo asks you to do performance testing for yahoo site, what are the inputs you ask from them?

2085

---

what are the functional test cases for enter user name,enter pass word,click on ok(only functional test cases)

2430

---

According to RBI rule how much money can be transferred through online banking at one time...?

2846

---

What are the phases involved in software testing life cycle?

1130

---

Do you know anything about Set Top Boxes?

9694

---

what exactly is heuristic checklist approach for unit testing?

3171

---

how can u prepare the test plan?

2226

---

Write test cases on duster

4919

---

HOW TO CREATE SRS REVIEW REPORT TO PL?

2352

---

Scenario A year ago we developed a standards compliant website for a client. Their site is very popular resulting in the client wanting to be able to track how it is being used by their users. The first part of this project is to create a Login function so that users can be identified on the website. The data supplied by users would have to be handled securely. You have been allocated this project to work on. You will be responsible for the task from start to finish and will be expected to give feedback to your manager. User expectations  The client wants their users to be able to login using a page that fits in with the website design.  Tom wants to access the website but doesn’t want his login information to be available to anyone else.  Paul doesn’t want to login to the website because he’s not a frequent user. Task Please provide some feedback on how you would do the following:-  Being the only Test Engineer on this task, what would your approach be for this requirement?  Identify the key areas for testing this page.  What tools if any, would you use to perform the testing, bearing in mind that the testing will be done without using an ‘automated test tool’.  Provide a sample test case that could be used for testing this page, for example as a word or Excel document.

1899

---

what comments have u given in peer review? tell me at least 3 comments what u have given? july27 brahma412@yahoo.co.in

1847

---

whar are the contents in db testing test case template

2019

---

what are the tests u did in entire project? when it did in the project? (means at the release build to end of project) plz explain clearly

2096

---

What will be the testcase for a uniquely generated number in the application?? i mean to say is, how will i conform the application is generating a unique value.... please do answer...

2146

---

If there is non reproducible bug which developer is not ready to agree, how you will convince him.

8867

---