u/Atypical_Foliant — reddlx

Hi everyone,
I'm trying to figure out the best way to phrase test checklist items for web applications.

I've seen three styles:

Keywords: "Reset button"
Assertions: "Reset button clears all filters and returns UI to default state"
Structured parameter combinations (like in classic testing books: within "valid config" they list spaces, Cyrillic, path separators for Win/*nix)

Which style works best in real-world manual regression and exploratory testing?
How do you write checklists so they remain useful for both juniors and seniors? Real examples appreciated.