jainbrijesh

 Profile Answers by jainbrijesh Questions by jainbrijesh

• Nov 4th, 2006

 

mainly two classes:Test cases for positive testing.2) Test cases for negative testing.Depends on u how u classify them.

tvudaykumar

 Profile Answers by tvudaykumar 

• Nov 24th, 2006

 

The various Test case design techniques are:

1. Equivalence partition

2. Marginal analysis

3.Intuitive test case design

4.Domain based test cases

5.Risk based test cases

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Aug 19th, 2009

 

1. Formal Test Cases
2. Informal Test Cases

1.Formal Test Cases
In order to fully test that all the requirements of an application are met, there must be at least two test cases for each requirement: one positive test and one negative test; unless a requirement has sub-requirements. In that situation, each sub-requirement must have at least two test cases. Keeping track of the link between the requirement and the test is frequently done using a traceability matrix. Written test cases should include a description of the functionality to be tested, and the preparation required to ensure that the test can be conducted.

What characterizes a formal, written test case is that there is a known input and an expected output, which is worked out before the test is executed. The known input should test a precondition and the expected output should test a postcondition.


2. Informal Test Cases
For applications or systems without formal requirements, test cases can be written based on the accepted normal operation of programs of a similar class. In some schools of testing, test cases are not written at all but the activities and results are reported after the tests have been run.

In scenario testing, hypothetical stories are used to help the tester think through a complex problem or system. These scenarios are usually not written down in any detail. They can be as simple as a diagram for a testing environment or they could be a description written in prose. The ideal scenario test is a story that is motivating, credible, complex, and easy to evaluate. They are usually different from test cases in that test cases are single steps while scenarios cover a number of steps.

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 26th, 2009

 

You can classify test cases any way you want to.  They can be classified as formal or informal.  They can be classified as functional or nonfunctional.  I classify test cases by folder label.  That is to say, whatever I label the folder that contains my test cases is what I classify them to be.  For example, all of my GUI tests are in my GUI folder; all of my security tests are in my Security folder; and so on.  Using this method, here are a few classifications:

1) Functional
2) GUI
3) Usability
4) Accessibility
5) Security
6) Load
7) Stress
8) Interoperability
9) Localizaton
10) Internationalization
11) Volume
12) Recovery