Aboo S

well this statment is very comprehensive but i thnk that a good tester or a QA engr.. should always sit and intend to crash the software for the first time. This can really help in learning and better quality of the software.

This sattament is very good.If there were some examples it would be very clear.

A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly. A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results.

I am mobile tester(QA) I write the test cases in mobile application but not satisfied, pls help anybody. I want to good test cases. How to write and expline.

Im a Qa tester, could anyone provide me with a checklist for Test case preparation.

send me some good test cases.
thank's.

Techniques for writing Good Test cases

1.First do some home work what do you want to test for a requirement

2.claisfy the type of requirement(GUI,Functional,Database..)

3.Gather maximum information related and affected areas with this requirement

4.In Deails section write this information(if you are using TD) which will be more useful for other testers

5.Use very simple English and general words in writing the description.(please don't show ur english talent here).All test steps should be low level.

6.Provide test data(if possible).

7.Write in details SQL Queries(it will save time while executing. Some people will not share their SQL knowledge in the scripts.)

8.Write clear Expected Result.

If you follow all the steps it will helpful to other testers and developes while execution and debugging(for developers

“A test case has components that describe an input, action or event and an expected response, to determine if a feature of an application is working correctly.”

yes, good explanation

Test cases are the series of steps to test the functionality of the features.
EX:
Suppose 'Login' button section of mail@gmail.com is a feature you need to test.
You need to write a series of steps to execute this button.
This series of steps can contain positive testing + negative testing.
Hope this information is relevent.

Test Case is a document which contents all possible scenerious to test the application.

Inorder to write good test case..
1. Understand domine
2. Business Needs
3. Study the requirements.
4. Arise Question on requirements.
5. Identify all possible scenerious.
6. Write test case for all identified senerious.
7. Review test cases.
8. Fixing comments.
9. Take approval.
10. Store it in repository.

ya it is very good blog spot it us to feature

The test case, is a set procedure that guides a tester to execute a test.
It is difficult to list test cases but I can give test ideas.

For a more realistic example of a testcase ideas, I have built the following sample testcase(ideas) for www.chetanaforum.com

1. In the URL field type in www.chetanaforum.com and hit the ENTER key
2. On the web page, for each link (login, Introduce urself, user opinion polls, chetanas happening, feeback etc.)
a. examine the link text
b. click on the link, and verify that the link works
c. verify that the new page is the correct page, as indicated by the link text
d. verify that the little black arrow correctly indicates the current page
e. click on the browser's BACK button
f. verify that the link's color changed to the vlink color
3. Every page should be tested in the same way

PLZ send to me answer

pls give valuable answers.......

Test Cases are the implementation of a test case design which will help the software tester to detect defects in the application or the system being tested. This should be the primary goal of any test case or set of test cases. When I write a test case, I think of both types of test cases, positive test cases and negative test cases. Positive test cases are those which execute the happy path in the application and make sure that the happy path is working fine. Negative test cases as the name suggests are destructive test cases which are documented with some out-of-box thinking to break the system.
A Test Case should be documented in a manner that is useful for the current test cycle and any future test cycles. At a bare minimum each test case should contain: Sr No, Summary or Title, Description, Steps to reproduce, Expected Results, Actual Results and Status of the test case or remarks.

The article of test case design was very understandable.
thanks for giving this

plz send How to write test case

very good..

give me some easy examples of couple of test cases....