Test cases can be written based on either a Functional & Requirements Specification Document or a Use Case Document or a Test Scenario Document....Now a test case document would be consisting of the following columns.
1.Test Case Id
2.Requirement Number or Traceablity Id
3.Summary Of Test Case
4.Test Steps (a)Preconditionsb) steps c) Post Conditions)
5. Expected Results
6. Actual Results
7. User Comments (Pass / Fail / OnHold)..also Defect Id for Build No
8. Review Comments (Modifications)
Sample Test Case:
File Open - Test case
Steps to reproduce:
1. Launch Application
2. Select "File" menu
File menu pulls down
3. Choose "Open"
"Open" dialog box appears
4. Select a file to open
5. Click OK
Result: File should open
2007-01-29 21:41:26
·
answer #1
·
answered by Mr.Sincere 1
·
0⤊
0⤋
Are you performing system testing or UAT testing. Accordingly the test cases differ. If you testing from developers side, build your test cases on the SRS (requirements placed by user)
List down the functions that the user has asked for and one simple method is write a test case which will enable the function to work properly and write to a test case to see what happens if the expected input is wrongly entered. Make it true once with the right set of data and make is wrong once with false data - special characters etc. You should programming logic to check whether your programme functions within the particular limits or fails. Then assess the no. of failures/bugs detected and report the same. Grade the bugs as severe, high, low etc.
If you are testing in UAT(from users side). Build your test cases on the requirements you communicated to your developer and check if the same works well. Make sure that when you are checking from the point of view of the user, you have taken into account all security threats that you might possibly face and see if the programmer has addressed them properly.
2007-01-29 21:56:36
·
answer #2
·
answered by indiangal 3
·
0⤊
0⤋
I'm assuming that you want to programmatically test this site? If you are using Java, I'd suggest using HttpUnit or HTMLUnit. First download JUnit, it has a nice cookbook on how to write test cases, it should take about 2 hours to read that and understand how to write test cases in Java. Then, you can read the documentation for HttpUnit and use that to build your test cases.
If you haven't chosen a language yet, consider using Ruby, with the Watir package. Watir lets you record tests as ruby scripts, and it's easy to edit these to extend them, or even to write your own. The only problem with Watir is that it is tied to IE, if I recall correctly. I've heard a lot of good things about the Selenium toolkit for testing, which is also Ruby based.
2007-01-29 21:50:36
·
answer #3
·
answered by Desi Geek 2
·
0⤊
0⤋
hi!
dere's noth to b worried.
to make test cases, just open excel and make points
1. what is the ultimate goal of the program and whether that is being fulfilled or not.
2. check all of the negative conditions.
3. check all of the positive conditions.
4. check opening and closing of both input and output files
5. check data in output files.
dere r othr also, give me ur mail id so dat i can send u d samples.
njoy yahooooooooooooooooooooooooo
2007-01-29 21:41:45
·
answer #4
·
answered by priya a 1
·
0⤊
0⤋
authentic now the DNA info may be used to make certain no count if the suspect feels like a woman (X-X chromosome) or a guy (X-Y chromosomes). at recent in basic terms stem cells may be used to clone a guy or woman yet sooner or later if differentiated cells could be cloned the info could be used to get carry of an 'same' twin different than, for the age hollow. Few human beings look like their toddler photos. besides the reality that there is not any statue of limitations for homicide, it incredibly is not likely that criminals may be cloned from the info. additionally, there could be ethical questions approximately cloning in basic terms a face.
2016-10-16 07:13:19
·
answer #5
·
answered by pantle 4
·
0⤊
0⤋