This is a discussion on Test Cases within the Testing Tutorials forums, part of the Articles and Tutorials category; Hi, Can any one guide me on building testcases for an insurence company and what information has to be gathered ...
|
|||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Re:Test Cases
Hi
First identfiy the core functionality of ur project. Then Divide into functionality wise (means recognise the screens) Then one by one start writing the test cases. Then any body can helping to you. Ask Functionality wise ideas. Thanks Raghu. Post edited by: sanereddy, at: 2005/01/29 14:35 |
|
|||
|
Re:Test Cases
Testcase can be a set of user actions with expected results.
Module can be divided in to set of testcases. Each testcase explains some part of functionality. It could be either functional testing or secuirty testing or GUI testing or load testing. Testcase includes nagative testing too. means what module should not do. Testplan defines the complete process of testing life cycle of projected module. Testplan explains core functionality of module , functional areas , resources , estimated hours , risk management , deliverable etc. testcases can be build up only after functional document get signed off from management team. Developers get the both functional and technical docs. But QA team requires only functional doc. Go through functional doc and analyze functional areas , define test cases, then explain each test case step by step with expected result. For example: Let\'s assime that your module is Yahoo.com You Write testcase as follows 1) Useraction : Open Yahoo module in browser by using following url. http://www.yahoo.com Expected Result:Yahoo home page should be displayed. 2)Click on Mail link on home page Ex.Result : User Name and password fields should be displayed. Cursor should be focused to \'Username\' field. 3)You can do negetive testing.i.e. enter user name only and click on Submit. It should display on error message. |
|
|||
|
Quote:
Whether you test the software through Manual or Use any tools, you have to write testcases for that. As when builds releases, this approved test cases are handed over to any tetser for execution and on the basis of Pass or Fail, Bugs/Issues/Errors are reported to Bug Tracking tool..... |
|
|||
|
Test cases are more important part for testing any software. On the basis of SRS, FRD, DRD and Use cacse, we identfy the functionalities for which we are going to write test case. Only on the basis of Effective Test cases, we test the software/build.
You test the Software or Build manullay or through some automation tool but in each case you need Test Cases. When you are going to use Black Box Technique for writing test case, in that case we don't require any language knowledge but if you are going to use White Box Technique for writing test case, in that case we require to know developing language frame work. |
|
|||
|
test cases
Quote:
If you have test cases can you send it to me, I am learner and it will be more benefited to me also. thanks sujata.v |