Userflows vs Test cases

Share
Userflows vs Test cases
Photo by Birmingham Museums Trust / Unsplash

Today I tried running the coverage mapper using the markdown guide that I created along with AI.

From the start, it wasn't clicking and I wasn't sure why.

Towards the end of the day I decided to look at QA wolf. A test automation software that I am modelling after.

After recording the way they manage it, I realised that there are some nuances.

Or I think there are.

Maybe I need to be mapping user flows, instead of test cases.

Or maybe I was mixing up my definition of the 2 and creating some deformed child.

I don't really know.

All I know is that the user flows need to be mapped first, not the edge cases. Like the user goes back, refreshes the page, blah blah.

I will map out the flows on qa wolf and, see how they do it, and try to emulate the same.

To get a high-level logical view of how the mapping will be executed, here is what Claude gave me.

This seems incorrect.

I don't know why.

Maybe we need to specify the effects at the start. But I want it to automatically figure it out.

Anyway, I'm too tired

I'll reason again tomorrow.