What Does <insert type here> Testing mean?

 

COS Testing (Acceptance Testing)

COS testing is the absolute minimum testing that can possibly be performed before any product is even considered for acceptance.  9 times out of 10, COS Testing by itself will not get your project accepted, but it is a milestone that needs to be reached before continuing on to other types of testing. 

In short, COS Testing takes the Conditions of Satisfaction of any given story and turns them into test cases.

Example 1.

COS:  When the user selects the Specified Charge option, they are able to enter the Specified Charge information with a $ amount and an effective date.

Test  Case 1:

1. Create a new contract for a subscriber
2. Add a new Specified Charge with a valid effective date (one that will actually generate data)
3. Generate a monthly fees report for that subscriber

Expected Result:

• The amount to pay the subscriber reflects the Specified Charge 
  

Test  Case 2:

1. Edit a contract for a subscriber
2. Add a new Specified Charge with a valid effective date (one that will actually generate data)
3. Generate a monthly fees report for that subscriber.

Expected Result:

• The amount to pay the subscriber reflects the Specified Charge and NOT the originally contracted amount.

Take the steps listed here with a grain of salt, as there may be more steps or some of these steps may be incorrect.  The point of this exercise is to demonstrate how a COS is translated into test cases.  You can see here that the COS requires at least two test cases as there are at least two ways of creating Specified Charges for any given contract.

Functional Testing (Including Negative Testing)

<coming soon />

 

Performance Testing

<coming soon />

 

Regression Testing

<coming soon />

Usability Testing

<coming soon />

 

UI Testing

<coming soon />