Is it so that each step in a test case must be specific and contain only one expected result? The context is for combine UI and functionality testing.

For example, when clicked button X user should be redirected to login page and the button X must be verify the blue color of button login.

Is it possible to combine with functionality test case?

  • The question here is, after you are redirected to login page, how does the button x from previous page verify the color for login button? Jan 4 at 6:20
  • The button x from previous page shown grey color as for default and its changed when there's click action on button Jan 4 at 6:34
  • Okay. So if I'm understanding right, the button x is grey. You click > Go to Login page > button x turns blue. Next question; Does it change label to Login or Login is a separate button here? Jan 4 at 6:37
  • Login is a separate button. Jan 4 at 6:45

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,

enter image description here


enter image description here

Either of them would be right as per my understanding.

The documentation rules/styles/formats can be customized based on the mutual understanding of the team. The actual point is a successful communication of work done and issues found (if any).

As long as your team understands what you're trying to convey, it's perfectly fine even if you write single line/paragraph test cases.


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.


This question is cool, thanks for posting it.

I've been working in BDD (behavior driven development) for a while now and this question goes to the heart of the breakdown of BDD as both requirements and test.

BDD Test in Gherkin might be something like:

When I open page http://whatever.com
Then the page contains button X
When I click on button X
Then button X is blue

As you see, there are several individual requirements and behaviors within that single sentence. There are many ways of expressing those requirements but the functional breakdown / specs of the user story flow there is key to understanding what to test.


It depends on who is the audience.

For which purpose you are writing the test cases and who is going to read and use your test cases.

If it's only for documentation purposes for manual testing - it's fine.

If it's primary purpose is to be used for test automation then it has to be very specific and step by step with expected results for each step separately.

If it's going to be used for both, then better to write with expected results for each step.

  • The OP's question is whether it is okay to have more than one expected results clubbed into one for a test step? Or each step should have only 1 expected result? Jan 7 at 10:08
  • Yes I understand. My point is , the structure of the test case very well depends on the purpose and audience of the document. If it's going to be used for automation then it's preferred to have very clear expected result for each step separately. Jan 9 at 18:59

The multiple expected result approach(w.r.t to a single test step) is usually preferred by software/security testing services at the initial level when we start building the product.

The steps-wise test case and multiple expected result format helps QA team to ensure the workflows/product is thoroughly tested and it further reduce the chances of missing any validation from QA's end.

However, preferring the multiple or single expected result layout is one's own choice and an engineer's comfort with the level of communication required in a project. Once the product gets stable over the years and workflows remain the same, we can refactor the test cases to be more generalized with a single expected.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.