Difference b/w Test case and Test?

Explain:

Difference b/w Test case and Test?:confused:

test is a general term for testing!
There can b many test cases while you are testing.
U have to think of all cases which can occur in program.
for eg if a exception occurs how does prog handle it etc.
so u should check with all possibilities!
:D

[QUOTE=vmshenoy;9046]test is a general term for testing!
There can b many test cases while you are testing.
U have to think of all cases which can occur in program.
for eg if a exception occurs how does prog handle it etc.
so u should check with all possibilities!
:D[/QUOTE]

You write test cases or test scripts to verify if the features will work according to the
requirement. Test cases can be derived as a use case scenario or a combination of different
requirments of that feature.

Test case test case: is a document that describing input, action or event and expected response to determine whether feature of application working correctly or not. Developing test cases: [list][*]design test cases for unit test event based on objectives of test[*]should be specifications derived tests[*]should consider equivalence partitioning[*]state transitions testing[*]design test cases that include abnormal situations and data.[*]design test cases for all known and expected error conditions[*]design test cases to be easily duplicated[*]each test case must be described input and predicted result and conditions under which the test has been run.[/list]test case design test case id: it is unique number given to test case in order to be identified. Test description: the description of the test case you are going to test. Revision history: each test case has to have its revision history in order to know when and by whom it is created or modified. Function to be tested: the name of function to be tested. Environment: it tells in which environment you are testing. Test setup: anything you need to set up outside of your application for example printers, network and so on. Test execution: it is detailed description of every step of execution. Expected results: the description of what you expect the function to do. Actual results: pass / failed if pass - what actually happen when you run the test. If failed - put in description of what you've observed. [u][b]test plan[/b][/u] a software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. A test plan states what the items to be tested are, at what level they will be tested, what sequence they are to be tested in, how the test strategy will be applied to the testing of each item, and describes the test environment. A test plan should ideally be organisation wide, being applicable to all of organisations software developments. The objective of each test plan is to provide a plan for verification, by testing the software. The software produced fulfils the functional or design statements of the appropriate software specification. In the case of acceptance testing and system testing, this generally means the functional specification. What to consider for the test plan: [list=1][*]test plan identifier[*]references[*]introduction[*]test items[*]software risk issues[*]features to be tested[*]features not to be tested[*]approach[*]item pass/fail criteria[*]suspension criteria and resumption requirements[*]test deliverables[*]remaining test tasks[*]environmental needs[*]staffing and training needs[*]responsibilities[*]schedule[*]planning risks and contingencies[*]approvals[*]glossary[/list]the test plan answers such questions as: [list][*]what is being tested?[*]what are pass/fail criteria?[*]when will each test occur?[*]what hardware and software environment is required?[*]what features must be tested?[*]what features will not be tested?[*]what are the responsibilities of individuals and organizations involved in the project?[/list]

[QUOTE=jainbrijesh;9045]Explain:

Difference b/w Test case and Test?:confused:[/QUOTE]

Hi,
Testing: To verify whether the product we are building is right, which means the product we build meets the needs of specification.Testing is a series of process.

Testcases: Testcase is a set of conditions or variables where in the tester will determine if the requirement is fullfilled or not. Testcases are generaly scripts which is used for testing an application.

[QUOTE=vmshenoy;9046][b]test is a general term for testing![/b]
There can b many test cases while you are testing.
U have to think of all cases which can occur in program.
for eg if a exception occurs how does prog handle it etc.
so u should check with all possibilities!
:D[/QUOTE]

[COLOR="Blue"][B]Test has different meaning then testing.Test and testing are two different terms.[/B][/COLOR]

[QUOTE=minhn_007;9086]You write test cases or test scripts to verify if the features will work according to the
requirement. Test cases can be derived as a use case scenario or a combination of different
requirments of that feature.[/QUOTE]

[QUOTE=Pradeep7;13610]Hi,
Testing: To verify whether the product we are building is right, which means the product we build meets the needs of specification.Testing is a series of process.

Testcases: Testcase is a set of conditions or variables where in the tester will determine if the requirement is fullfilled or not. Testcases are generaly scripts which is used for testing an application.[/QUOTE]

[COLOR="Red"][B]Again test and testing are two different terms.Please read question carefully before answering the question. [/B][/COLOR]

Testcase is a set of input values ,execution preconditions,expected results and execution postconditions,developed for a particular objective.
Test : A set of one or more test cases.