An input value cell or an expected value cell is normally handled by parsing the cell contents based on the value type. Special processing of cell contents is implemented by a set of classes known as cell operators. There is a variety of cell operators provided, and we can Write Our Own Cell Operator.

Standard Cell Operators
These are the standard cell operators used in fitSharp by default.

Check operators are used to process an expected value cell.

• Check Empty
• Check Symbol Save handles Symbol Values

Compare operators are used to compare an expected value cell to an actual value.

• Compare Empty
• Compare Error
• Compare Exception
• Compare Fail
• Compare List
• Compare Numeric

Parse operators are used to convert input and expected cell contents into a .NET object. The Parse Default behavior is used if none of the following operators are applicable.

• Parse Array
• Parse Blank
• Parse Boolean
• Parse Byte Array
• Parse Date
• Parse List
• Parse Null
• Parse Null Array
• Parse Symbol handles Symbol Values
• Parse Table
• Parse Tree

Optional Cell Operators
These operators can be added to fitSharp to modify the standard behavior.

• Compare Ends With
• Compare Floating Point
• Compare Interal Range
• Compare Reg Ex
• Compare Starts With
• Compare String
• Compare Substring
• Find Member Pattern Operator
• Parse Quoted String
• and others ...

There are three ways to add cell operators so they will used to process cell contents. By default, any custom operators will come in at lower priority than the built-in ones, which means the built-ins take precedence. To register custom operators to run before the built-ins, use AddFirst instead of Add.

• In a Suite Configuration File:

  <suiteConfig>
      <Fit.Operators>
          <Add>My.Operator</Add>
          <AddFirst>My.Important.Operator</AddFirst>
      </Fit.Operators>
  </suiteConfig>

• In a story test:

  |configure|processor|add operator|My.Operator|
  |configure|processor|add operator first|My.Important.Operator|

• In fixture code:

  Processor.AddOperator("My.Operator")
  Processor.AddOperatorFirst("My.Important.Operator")

AddFirst can be useful if a custom operator needs to see the raw cell contents before Symbol Values are expanded, for example.