Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. Join them; it only takes a minute:

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 have made a notepad in c and i want to add find & replace feature so i just want some test case for that feature so that it works fine in notepad editor.

share|improve this question

closed as not a real question by corsiKa Aug 2 '11 at 19:40

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

I think 'FrustratedWithFormsDesign' answered this nicely over at – Todd Bumbarger Aug 2 '11 at 14:57
This question was asked and answered, as @Todd pointed out, on another site. The question does not appear to really have had a lot of research or effort added to it, more like someone is looking for help with an interview or test question, hence the down vote. – TristaanOgre Aug 2 '11 at 16:06
Downvoting for the reasons TristaanOgre mentioned. – user246 Aug 2 '11 at 16:09
I agree with Tristaan and User246; this question shows little effort – BrMcMullin Aug 2 '11 at 17:05
Welcome to, rohit! I notice a distinct lack of a question here. There are a great number of different ways to test, and it would be much better if you could provide some more details: background of why you wrote it, what you hope your tests will accomplish, how comprehensive these tests are intended to be, and the like. If you edit this post, post a comment to let me know so I can reopen it, or feel free to post a new question that... actually has a question :-) One of the hallmarks of a good question is showing what research you've already done so others can pick up where you left off. – corsiKa Aug 2 '11 at 19:43

I'd suggest you do the following:

  1. Start with a list of things the feature is supposed to do. You should already have this from when you created the feature. If you have a function specification, use that to create the list.
  2. For each item on the list write some test cases to test the item.
  3. Edit your question and add the list of tests you created. Ask if your test cases are good or not.
share|improve this answer

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