3

It's totally okay to write a combined expected result for all the steps of a test case. It's also normal to write single expected result for each individual step. Taking your example, your case can look like, Or Either of them would be right as per my understanding. The documentation rules/styles/formats can be customized based on the mutual understanding ...


3

This is a pretty common situation that I was in and have seen others in. Being in the "middle tier" of experience can feel like hitting a wall or even a plateau. You want to move upward but feel stuck. It also doesn't help that the industry has a focus of either "manual" or "automation". It's very "or" minded instead ...


2

A test case is just a document regarding your testing. If it communicates the necessary information for the target audience, then it is fulfilling its goal.


Only top voted, non community-wiki answers of a minimum length are eligible