praveenrachamalla

 Profile Answers by praveenrachamalla 

• Apr 28th, 2006

 

Test Plan : it is a document that describes Scope approach and focus of Testing effort.

Use Case : it is a Low Level Design document that captures the Business Logic at a component, screen or Submodule level.

kankanalapoornima

• Apr 29th, 2006

 

 hi sir

i want diff b/w sanity and smoke testing . If possible plz send to me that in formation  to my mail

thankx sir

santoshkumar pvh

 Profile Answers by santoshkumar pvh Questions by santoshkumar pvh

• Apr 29th, 2006

 

Test plan : It contains introduction to the client company,scope,overview of the application, test strategy,schedule, roles and responsibilities, deliverables and milestones.

Use Case : It is nothing but user action and system response. It contains the flows typical flow, alternate flow and exceptional flow. Apart from these it also has a pre condition and post condition.

varma

• May 1st, 2006

 

The general definition (related to Hardware) of Smoke Testing is:
Smoke testing is a safe harmless procedure of blowing smoke into parts of the sewer and drain lines to detect sources of unwanted leaks   and sources of sewer odors.

It it is related to s/w, the definition is
Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details.

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. It normally includes a set of core tests of basic GUI functionality to demonstrate connectivity to the database, application servers, printers, etc.

vikas sharma

• May 30th, 2006

 

hi.

sanity testing - is basically to check whether the application is having any negative impact on the existing hardware and software.

smoke testing- is basically to check whether the main functionality  of the application is working properly or not.

at the very first we just check these two aspects. if an application fails then we dont do further testing.

sudhakar2068

 Profile 

• Sep 26th, 2006

 

Test Plan: A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. Ref IEEE Std 829.

 Use Case: The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities

sudhakar kolla.

My Email:kollasudhakar2005@yahoo.co.in.

My Number:09819859346.

Ravi Kanth

• Jun 25th, 2007

 

Sanity Testing: Its an indepth testing of an application. Tests every feature throughly. Done after Smoke testing.


Smoke Testing: This type of testing is done when the build arrives for testing. Tests the major functionalites of an application that are most frequently used.

Sujatars

 Profile Answers by Sujatars 

• Aug 15th, 2007

 

Use Case : It is a function that captures the Business Logic at a component, screen or Sub-module level. It describes the functions, how the application will perform.

Test plan : is the document which provides overall directions to all the testing activities.

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Apr 12th, 2009

 

Test Plan is a document, which says how testing can be carried out, by specifying scope, schedules, resources, deliverables, due dates, etc...

Use case consists of user actions and in response application response for a particular functionality or business process

rammohan19

 Profile Answers by rammohan19 

• May 8th, 2009

 

Test Plan: It is a strategic document, which describes how to perform a particular task effectively, efficiently and optimized way.

Use case: It is a description of functionality of certain future of an application in terms of actors, actions and responses.