3

How should I create a test case, or what should the test case be, when the scenario is for a function that shouldn't be in the system?

I'm creating test cases based on the FSD (Functional Specification Document). Our FSD is composed of Requirements, Processes, and Fields for specific modules. While executing my test case, I have encountered a button that isn't in the FSD. How should I create a test case for this?

I am thinking of something like "System must not have buttons that aren't stated in the FSD" but that seems wrong.

I'm kind of new in QA, and in our company, we have a standard to use the word "System must, System must not, User must, or User must not" in all of our test cases.

Improve this question
1

1 Answer 1

Reset to default
2

Your test case seems fine, if that is truly the requirement. Before going further, I would check with the Product Manager or someone if that functionality is intended (and just not documented in the FSD).

If the FSD is truly "the bible", I would phrase the test case "System must not expose functionality that is not documented in the FSD", but this is just a wording preference on my part.

Improve this answer
1
  • thank you for the asnwer or kind of advise. For us, we strictly based on the FSD it's our kind of ACE when arguing with the Dev team.
    – Vincent Dapiton
    Commented Aug 26, 2017 at 23:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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