Because you have 2 test cases; that's the only reason this looks confusing at all.
Functional test case: Do I get a correct (correct may mean correct-enough, example 999.9 might be acceptable for your domain) answer to my question.
UI experience test case: Can user see the menu, click it and get to a entry screen. Does the user get confirmation dialogs and ...
Defiantly this should not be ignored, but the approach should depend on how "up to date" the test case and/or the documentation is. The course of actions in my opinion should be:
If you have no doubts about the test case and the business requirements - fail the test case,
Ask your project team / test manager - maybe this step is obsolete as ...
In my tests, I report after each step. I'm using TestProject, so they have a great mechanism for the reports, but you can definitely do it by yourself (for example using logs mechanism).
That way, you don't have to fail the entire test if you think that this step is not critical, but still, document the failure.
Disclaimer: I am employed by TestProject.
What you should do depends on the processed followed by your team and what kind of testcase we are dealing with.
What should happen in any case is that a defect is raised, because either the software contains a bug (if the confirmation screen should have been shown), or the testcase is incorrect in expecting the screen is shown unconditionally.
If your ...
Honestly, in this example, I'm confused about why the confirmation dialog should appear at all. Isn't it just a useless step that slows down the user? There might be some reason for that that I can't get from the short description, but I'm a bit suspicious, that's why I'm bringing it up.
And I think that's exactly what you should do with the rest of your ...
Actually, you have multiple tests on the above description.
1.1 - Open the menu
Here you have hidden all complexity of start-up the application
1.2 - and select F X
Here you test that an even is trigged when a button is selected
2 - Confirmation dialog appears
Here you test that the dialog appears when an even is trigged.
3 - Function screen appears
I guess this might depend.. First of all everything has its own cost. If you have lots of such tests it might take lot of time to raise each such defect. However the defect might get low severity and low priority and will never be handled.
Another thing is that the use case itself might be very unlikely, or the area itself is to be reworked as per team ...
If step is not important would not have been included in the test.
Failure of any step, should result in the entire test failure.
Having or not having workarounds or how the failure impacts user experience might only define the defect severity.
The defect has to be registered.