How can we write a good test case?

Can u please give me deatil notes for manual testing and Black Box testing starting from the basics.. 
 
 
thanks in advance. 

HI, 
A good Testcase is one that as ahigh probability of finding an error an as at un discoverederror.

Could you please give me the details of automating a browser testing. Also let me know if automation is perfectly possible for the entire project. 
 
thanks in advance.

PLZ GIVE me detail how to right good test cases

how to conduct a testing in Broken-links using winrunner?

this is a very good apporchunity to learn more

Essentially a Test Case is a document that carries a Test Case ID no, title, type of test being conducted, Input, Action or Event to be performed, Expected Output and whether the Test Case has achieved the desired Output(Yes \ No)Basically Test cases are based on the Test Plan, which includes each module and what to be tested in each module. Further each action in the module is further divided into testable components from where the Test Cases are derived.Since the test case handles a single event at a time normally, as long as it reflects its relation to the Test plan, it can be called as a good test case. It does not matter whether the event passes or fails, as long as the component to be tested is addressed and can be related in the Test Plan, the Test Case can be called a good Test Case.

Essentially a test case is a document that carries a Test Case ID no, title, type of test being conducted, Input, Action or Event to be performed, expected output and whether the Test Case has achieved the desired Output(Yes \ No)
Basically Test cases are based on the Test Plan, which includes each module and what to be tested in each module. Further each action in the module is further divided into testable components from where the Test Cases are derived.
Since the test case handles a single event at a time normally, as long as it reflects its relation to the Test plan, it can be called as a good test case. It does not matter whether the event passes or fails, as long as the component to be tested is addressed and can be related to in the Test Plan, the Test Case can be called a good Test Case.

Essentially a test case is a document that carries a Test Case ID no, title, type of test being conducted, Input, Action or Event to be performed, expected output and whether the Test Case has achieved the desired Output(Yes \ No)
Basically Test cases are based on the Test Plan, which includes each module and what to be tested in each module. Further each action in the module is further divided into testable components from where the Test Cases are derived.
Since the test case handles a single event at a time normally, as long as it reflects its relation to the Test plan, it can be called as a good test case. It does not matter whether the event passes or fails, as long as the component to be tested is addressed and can be related to in the Test Plan, the Test Case can be called a good Test Case.

Suspect the functionality of the application, try to break  its functionality in all possible ways.

Lavesh Wrote: PLZ GIVE me detail how to right good test cases

prasad Wrote: how to conduct a testing in Broken-links using winrunner?

Please If you know the Answer for a question .give that. or else submite question  aging.

This answer for sub question.

Broken link is a property of the Text Link.

Function:

brokenlinks(linkname, URL, YES/NO), by default it will NO.

Hi,

Good Testcase is to cover the all functionality of that project.

We can use to Test this Testcase it will satisfied the All conditions(Positive / Nagative).

hi,

   Good test case is one which will Break the developers logic or Creating a test case which will fail.

We can write a good test case such way that it will test the functionality of the module as per the the requirement. Henceforth to write a good test case one should refer to Functional Specification Document (FSD)and Design Specification Document (DSD).

hai radha, please tell me how to write the integration test plan and test case

A Good 'Testcase'  is has not morethan steps and cover more functionality in the single shot.

How can we write a good test case?

we can write a good test cases by using the equvalence and aboundary value analysis

A good test case is one which finds undiscovered error

Hi,

When ever you are writing a good test case you have to concentrate on its repeatability and performance of finding the bugs.  Think in different directions. Here is a example:


I am checking a field of one application suppose I am having test case, but, it must be tested on may 1st (this is the information having in the test case).
This is not a good test case. The test case must be repeatable. But it should find the new bugs.

Thanks

Subramanyam

By inserting GUI check points.
GUI check points checks the broken-links in the web app.

Suspect the functionality of the application, try to breakits functionality in all possible ways.

A good test case is more likely to detect the defect hidden in application you are testing.

A good test case is one, by which when the test case fails/passes, the result analyser should be able to find the reason of fail/pass easily.

Test case should find the high probabilty of errors
It should cover all the functionality
It should'nt be redundant
Neither too simple nor too complex
a good test case should not be dependent on the result of the previous test case

We can write good test cases by using

ECP (Equivalence class partition)
BVA  (Boundary Value Analysis)
EG   (Error guessing)
CEG (Cause Effect Graph)

I hope this will be helpful

We execute test case manually and compare expected value vs actual value

Accurate - tests what its designed to test
Economical - no unnecessary steps Repeatable,
Reusable - keeps on going
Traceable - to a requirement
Appropriate - for test environment, testers
Self standing - independent of the writer
Self cleaning - picks up after itself

A good test case should cover all the functionalities as per the budget and risk of the Project. It should be in good order and should have both Positive and Negative test cases. It should have been written in such a manner that the tester who is going to execute the test cases will find himself comfortable in executing the test cases.

A Test case should cover more functionalities without any repeat and which should be understandable to the developer when a bug is raised.

Test Case A test case is a unique statement which covers the completeness and correctness of a given functionality.

test case designed documents contains set of procedures that has to be executed to find out the bugs. it contains test case id, test case description,test case procedure,test input,expected result and actual result. once you finish writing these test cases execute the test cases, if the actual result is equl to expected result then the test case is passed if not equal then it is failed

Any test case should be independent.Test cases should be so informative that any lay man should be in a position to understand as to what is expected Test cases should have informations like : test case id,test case name,project name,module name,prepared by,reviewed by, objective of the test case. The columns should be : input data,actual ,expected,result.

A test case is a document containing series of action,events,input,expected result and actual result. The optional fields are TestCase ID,Test Case Description/Procedure, Expected Result, Author, Check Box to determine whether that step can be automated or not, Actual Result,Status. A good test case is one which covers all the possible testing steps based on the Requirements specification to find the defect. Test cases can be of certain testing styles like domain testing or risk-based testing. 

Test cases are written from the functional requirements. Test case is the step by step process to check the functionality of the application.

Eg:
Functional Requirement:

login name: Text field should accept alphabet characters

Test case id: T01
Test case name: Login Name
Author: xyz


Step1 :1
Scenario: Login in to PI client and add name

Step description:
Add name 'Sweta1' in the text field and click tab
Expected result: The system should not accept sweta1 and show error 'INVALID character'

Actual result: The system accept 'Sweta1' and after clicking tab did not show any error
Pass/Fail: F
Defect ID: DC01

Comment

A good test case is one which we can make it based upon the SRS requirements 

To write a good test case, it must:
 
1) contain all of the necessary preconditions
2) contain all of the necessary steps 
3) have clear expectations
4) have clear pass/fail criteria
5) be written in a way that a person can execute the test without any prior knowledge of its functionality
6) be mapped to its requirements
7) have appropriate priority attached to it

There is no proper method or procedure is there to follow to write a Good Test Case but only thing is based upon the requirements how much negative test cases are written to capture the bugs are said to be known as good test case

There is no proper method or procedure is there to follow to write a Good Test Case but only thing is based upon the requirements how much negative test cases are written to capture the bugs are said to be known as good test case

good test case means fulfilling the requirement. it is nothing but good test case writing. it should be very understandable and to reach the up to client requirement.

@ everyone who is posting unrelated questions within answer thread

Your acts are really annoying. Please use the correct forum to post your questions and get quick answers. How difficult it that?

Anyhow here is a link to a great paper : http://www.kaner.com/pdfs/GoodTest.pdf