rslc check establishes properties of the implemented calculations and input constraints.
Generated requests exercise those declared rules. Independently calculated cases test whether selected premiums agree with the intended rating algorithm.
Rate generated requests
Generate requests that pass every rule, and save them as JSON lines:relativities-examples/rsl/dwelling-fire:
Rate generated bad requests
Add--invalid. Each row breaks one rule and records the refusal it expects:
mutation names the change: a missing dwelling, then too many items. The generator breaks list
lengths, repeated keys, missing records and choices between record kinds. Write your own cases
for number ranges and for rules that read several inputs.
Match the filed rating examples
A filing often prints worked examples. Rate each one and compare the premium exactly. These expected values come from the invented manual in the tutorial; replace them with independently established expectations for your filing:- Add one case at each band edge, such as protection classes 3 and 4.
- Add one refusal case for each rule with a code, and compare the code.
- To compare a value inside the calculation, rate with
detailed=True.
Related
- Use the rslc commands covers each
rslc inputsoption. - Refusals lists the codes a refusal carries.