Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've written an Integration program that produces files from a source set of data and converts it to a target data file. These files contain field/record information that must be validated by our clients using their validation methods.

I plan to create numerous test cases and expect to receive information on how well the data validated so I can tweak my program.

I want to create a test case that I know will not pass their validation, however I need to know if their validation methods are picking up basics such as the file structure and layout.

I am trying to prevent the situation if all my test cases pass, but later on the files were not in the correct format the client needed.

Do you feel this is a good idea and would I get any valid information from it?

share|improve this question
up vote 9 down vote accepted


that's not a bogus test case, it's a valid test for expected exceptions

share|improve this answer
Negative test cases are just as good as positive ones. Does it break the way we expect.... – Jon Raynor Sep 1 '11 at 0:40
Or perhaps more accurately "does it work they way we intended instead of breaking?"? – AndyBursh Sep 1 '11 at 8:49

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

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