Monday, May 7, 2007

Testing faq page2

What are 5 common problems in the software development process?
poor requirements - if requirements are unclear, incomplete, too general, and not testable, there will be problems.
unrealistic schedule - if too much work is crammed in too little time, problems are inevitable.
inadequate testing - no one will know whether or not the program is any good until the customer complains or systems crash.
featuritis - requests to pile on new features after development is underway; extremely common.
miscommunication - if developers don't know what's needed or customer's have erroneous expectations, problems are guaranteed.

what is difference between test plan and usecase?
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.A usecase describes how a end user uses specific functionality in the application

what is difference between smoke testing and sanity testing?
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.
In relation to software, 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 brief test of major functional features of a software application to determine if its basically operational(or Sane)

Differentiate between Static and Dynamic testing?
Test activities that are performed without running the software is called static testing. Static testing includes code inspections, walkthroughs, and desk checks. In contrast, test activities that involve running the software are called dynamic testing. Static: Document review, inspections, reviewsDynamic: Build testing/testing code/testing application

What is the Requidifference between rements & Specifications?
Requirements: means statements by the customer what the system has to achieve.
Specifications : are implementable requirements

What is the difference between statement coverage, path coverage and branch coverage?
Statement coverage measures the number of lines executed.
Branch coverage measures the number of executed branches. A branch is an outcome of a decision, so an if statement, for example, has two branches (True and False).
Path coverage usually means coverage with respect to the set of entry/exit paths

No comments: