Version 3, I think.

We first started with an excel sheet for test cases(version 1)

Version 2 was the tracker + element IDs + Excel sheet output + Claude.

So this is version 3.

Problem: New features break old features. Old features are too complex to test off the top of my head. (complex meaning some toggles enable a whole branch of other features)

Solution: A process of generating a coverage map of all flows, manually testing them, and validating the tested flows using data.

I was tempted to add the tracker in this iteration, but I am sure something will come up in the other components.

It's a bit harder to define scope when I don't know what the solution is going to be.

So here is my attempt at predicting the future.

The deadline is Saturday, so that is fixed.

Sprint deliverables

User Flow generation

[ ] A markdown for buildprint to map all possible user flows into Excel csv template.

[ ] Run on Arkhitect and verify if it covers all cases.

Excel csv

[ ] See if there is a better way to display test cases and permutations.

Everytime I open the testcases sheet, my brain shuts off.

How do I make it a bit more fun?

Data Validation

[ ] Use buildprint to validate the test cases that ran and check whether they were actually correct.