Value Pairs

Value pairs - pairs of parameter values, normally used include invalid pairs and married pairs (those value pairs that are interdependent with each other). For example: When role = student the classification is either Freshman, Sophomore, Junior, or Senior When role = staff the classification is either Adjunct, Assistant, Professor, or Administrator So in this example role and classification are value pairs in that the valid values for classification are dependent on the role. See: Using Value Expansions and Value Pairs to Handle Dependent Values

  • Invalid pair - a pair of values that are not possible. For example, the Internet Explorer browser is not available on the Mac operating system. So if two parameters in the test plan are operating system and browser we can use the invalid pair setting to indication that the parameter value of Internet Explorer is not valid when the operating system parameter value is Mac.

    Detailed example: Hexawise lets you set invalid pairs so that the test cases generated do not include such invalid test settings.

  • <li><strong>Married pair</strong> - married pairs allow you to mark all the parameter values as invalid in a given situation.  When some of the paramater values are valid and some are invalid you must use the invalid pair option to make that clear.
    

    If all the parameters values are invalid then the married pair option is more efficient (otherwise you just have to mark every parameter value pair as invalid). For example if one of the paramaters is payment method and another is credit card type, then using the married pair setting can set the credit card type only to be used when creating a test script when the payment method is "credit card." Detailed example: how do I prevent certain combinations from appearing using the "Married Pair" feature?