Test a term insurance comparison table

The flow under test

Each row carries three values and the table carries one conclusion, and all of them have to agree.

The cheapest callout is asserted separately, and it has to name Sundial at 5,865.00. A table sorted correctly with a cheapest label pointing at the wrong row is a specific and very plausible defect.

The test file

Every row asserts cover and term alongside the premium, because a cheaper quote at a lower cover is not a cheaper quote and that is the easiest way for a comparison to mislead.

---
mode: testing
url: https://my-testing-repo-main.vercel.app/policybazaar-clone-app/term?reset=true
max_steps: 45
tags: [policybazaar, insurance, comparison]
---

# Policybaazar 27.1: Term insurance comparison

Catalog objective: enter profile details and view the term plan comparison table.
Key assertion: plans are listed with premiums and cover amounts.

## Enter the profile
Type "Priya Nair" into "Name", set "Age" to "32", leave "Gender" on "Female", leave the tobacco box unticked, select "₹10,000,000.00" in "Life cover", select "30 years" in "Policy term".

## Compare
Click "Compare plans" and verify a "Plans for you" card appears showing "Plans found" of 4.

## Verify the table lists premiums and cover
Verify the table lists "Sundial Insurance" at "₹5,865.00", "Kestrel Assurance" at "₹6,274.00", "Meridian Life" at "₹6,820.00" and "Harbour Mutual" at "₹7,775.00", each with a cover of "₹10,000,000.00" and a term of "30 years".

## Verify the cheapest plan is called out
Verify "Cheapest" reads "Sundial Insurance at ₹5,865.00".

The plan count is asserted before the rows, which proves no insurer was silently dropped from the comparison.

Step by step coverage

A profile, a comparison, the rows and the conclusion.

Asserting the plan count catches an insurer dropping out of the comparison, which is a commercial problem as much as a technical one.

Running it

kane-cli testmd run tests/policybazaar/term-comparison_test.md

Add a tobacco variant, since the loading should move every premium and a profile input that fails to reach the pricing engine is a silent mispricing.

Comparison data changes constantly while the page around it does not. Running Kane CLI in CI covers catching that, and deriving a suite from requirements covers keeping expected figures anchored.