Test Cases and Test Plans

Hi Angelina,

Test case is set of input values, execution preconditions, expected results and execution Post conditions, developed for a particular objective or test conditions, such as to exercise a particular program path or to verify compliance with a specific requirement.

Test Plan: A test specification is called a test plan. A test plan is documented so that it can be used to verify and ensure that a product or system meets its design specification. Actually test plan describes what to test, how to test, when to test. It defines the test strategy and organized elements of the test life cycle, including resource requirements, project schedule, and test requirements

Purpose

Test plan document is prepared by the test lead, it contains the contents like introduction, objectives, test strategy, scope, test items, program modules user procedures, features to be tested features not to tested approach, pass or fail criteria, testing process, test deliverables, testing, tasks, responsibilities, resources, schedule, environmental requirements, risks & contingencies, change management procedures, plan approvals, etc all these things help a test manager understand the testing he should do & what he should follow for testing that particular project.

Test plan is a high level document, which explains the test strategy, time lines and available resources in detail. Typically a test plan contains:

-Objective

-Test strategy

-Resources

-Entry criteria

-Exit criteria

-Use cases/Test cases

-Tasks

-Features to be tested and not tested

-Risks/Assumptions.

 

 

Hi Angelina,

Difference between SRS and BRS/ Test plan and Test Case 

What is SRS and BRS . and what is the difference between them.

You can find all your answers here.

http://superfastcomputer.com/images/bart_simpson.jpg

Other answers can be found in the group FAQ at:

http://www.faqs.org/faqs/software-eng/testing-faq/

Wayne Woodruff
http://www.jtan.com/~wayne


----------------------------------------------------------------------------
If this post helps you, then click "This is Correct Answer"

Hi angelina,

Test Plan:
A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements. A test plan is usually prepared by or with significant input from Test Engineers.

Depending on the product and the responsibility of the organization to which the test plan applies, a test plan may include one or more of the following:

1.Design Verification or Compliance test - to be performed during the development or approval stages of the product, typically on a small sample of units.
2.Manufacturing or Production test - to be performed during preparation or assembly of the product in an ongoing manner for purposes of performance verification and quality control.
3.Acceptance or Commissioning test - to be performed at the time of delivery or installation of the product.
4.Service and Repair test - to be performed as required over the service life of the product.
5.Regression test - to be performed on an existing operational product, to verify that existing functionality didn't get broken when other aspects of the environment are changed (e.g., upgrading the platform on which an existing application runs).

Test case:
A test case in software engineering is a set of conditions or variables under which a tester will determine whether
an application or software system is working correctly or not. The mechanism for determining whether a software program
or system has passed or failed such a test is known as a test oracle. In some settings, an oracle could be a requirement
or use case, while in others it could be a heuristic. It may take many test cases to determine that a software program
or system is considered sufficiently scrutinized to be released. Test cases are often referred to as test scripts,
particularly when written. Written test cases are usually collected into test suites.

Best Link

Hope it help you....