Resources indirectly associated with the Line/Job Context API

Feature files and step classes

Feature files and step classes contain step method code used for testing a specific line of business and job. But, neither of these files directly reference any context API. Feature files reference only step definitions in step classes, and step classes reference only Context Factory.

TagProcessorInfo

Every feature file that has LOB-specific scenarios starts with an LOB tag, such as @personal_auto or @homeowners. This tag identifies the LOB to be used for the scenarios.

Similarly, every feature file that has job-specific scenarios starts with a job tag, such as @submission or @policy_change. This tag identifies the job to be used for the scenarios.

TagInfoProcessor contains code that sets the product code and the job subtype to the appropriate values for each LOB-specific or job-specific scenario.

TagInfoProcessor is not directly associated with the Line/Job Context API. But, it contains code necessary for setting up pre-condition data for every line-specific or job-specific scenario. (TagInfoProcessor does not play a role in testing LOB-agnostic and job-agnostic scenarios.)

ProductCode

ProductCode is an enum that identifies the lines of business supported by Behavior Testing Framework.

For each line of business, there is an enum value (such as HOMEOWNERS or WORKERSCOMPENSATION) associated with the corresponding typecode from PolicyCenter (such as HOPHomeowners or WorkersCompensation).

Like TagInfoProcessor, ProductCode is not directly associated with the Line/Job Context API. But, it contains code necessary for setting up pre-condition data for every line-specific or job-specific scenario. (ProductCode does not play a role in testing LOB-agnostic and job-agnostic scenarios.)