Prepare for your Next Interview
|
Welcome to the Geeks Talk forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
This is a discussion on testcase format, manual testing procedure within the Test Cases forums, part of the Software Testing category; hai everybody can anybody help me. i am working as a software tester in indian company. our project is online payment project. we are not having requirement specification. how can ...
|
|||||||
|
|||
|
testcase format, manual testing procedure
hai everybody
can anybody help me. i am working as a software tester in indian company. our project is online payment project. we are not having requirement specification. how can i write testcases and what is the procedure. what tests i have to conduct. what is the exact testcase format. |
| The Following User Says Thank You to nuthan.testing For This Useful Post: | ||
| Sponsored Links |
|
|||
|
Re: testcase format, manual testing procedure
hi friend...
i don;t think so i can tell u the exact test cases format because different companies follow different format..the format which i follow is attached and hope it helps Thanks deepasree |
|
|||
|
Re: testcase format, manual testing procedure
Hi,
You can create a test case by using Excel sheert with the following format 1 Topic - Give a opt topic for the testcase 2 Description - Explain about the testcase 3 TestSteps - Explain how to Navigate to the particular testcase 4 Expected Results - Describe the Expected Results 5 Actual Results - Describe the Actual Results 6 Test Status - Write whether the testcase is passed or failed 7 Bug Case Number - If the testcase is failed, Log a bug and mention the bug number in this column 8 Date - Write the date As deepashree said, different companies follow different format that I followed.Hope this helps you!! Thanks Radha |
|
|||
|
Re: testcase format, manual testing procedure
Quote:
You Have not any Req. Specification ,for your Online payment system . In this case , Explore Your Project , and devide it in to different Category. Like - UI , Functionlity , etc. and Create different Senerio for individual . and start weiting test cases for individual senerio. This will help you to create and cover all cases. Is there any query...always wel come regards, Sudhansu |
|
|||
|
Re: testcase format, manual testing procedure
QTP identifies the objects while recording, QTP take the classes & properties (Mandatory, Assistive & ordinal identifier) go to seach the object object in application. The QTP identify the object based on the mandatory Properties, QTP stop leaning else take the Mandatory & assitive properties(one by one)then to find the object, QTP stop leaning else take the ordinal identifier then QTP should be identify the objects in app.Finally the object is identified the object will store in OR along with the Description.
While running, Take the script go to OR find the objects, is present take description go to app. and do the process what we are record. |
|
|||
|
Re: testcase format, manual testing procedure
hi,
U have any spec, then we write the write Test scenario / test cases based up on u'r app. functionallity. In My company we are following the test case template . -------------------------------------------------------------------------------- | TC_ID | TC_Des | Procedure | Test Data | Expected_Res | Actual_Res | Status | -------------------------------------------------------------------------------- 1. TC_ID - It refers the Uniqe ID 2. TC_Des - It tefers the description of the test case. 3. Procedure - what we r going follow to test. Step by step Procedure. 4. Test Data - It is prepared by 6 techniques 5. Expected_Res- What u r expecting in the app. 6. Actual_Res - What is the actual u are getting in the app. 7. Status - 5 & 6 is same, it is 'pass' else 'fail' these Test cases map to the relates Requirement fields in RTM. |
|
|||
|
Re: testcase format, manual testing procedure
I've a question..
If i'm testing the log in page, then there will be different steps like(e.g) 1. steps : enter valid username(user1) & password(pass123#) & click 'Login' Expected result:The user should be allowed to log in application Actual result: ... 2. Steps :Enter invalid username(1243) & password (###)& click on login Expected result : It should display the error messages for invalid data So my qn is whether these steps 1 & 2 are called test cases liketest case1 & test case2 Or the whole login page module will be identified as a single test case? |
|
|||
|
Re: testcase format, manual testing procedure
Quote:
In u r query step 1 & step 2 will be considered as Test case 1& Test case 2 . Test case 1 is called +ve test case & Test case 2 is called -ve test case. All the test cases will be considered as test plan for the scenario Login page. If u want to test a login page ,Inaddition to the steps 1&2 ,u need to check all the possibilities like alpha numeric characters, 0-9, etc. Try to include more -ve test cases, stress & performance test cases Thanks, Riju. Last edited by rijus; 08-27-2009 at 11:39 AM. |
|
|||
|
Re: testcase format, manual testing procedure
Quote:
thanks. U asked to add stress & performance test cases. I do manual testing.so which stress & performance test cases can i add for the log in page scenario? also what should we call the excel document that contain all teh test cases for any project? test plan or test cases document for project-x bcz as per my understanding test plan is different thing so please let me know which naming standard should i follow? Last edited by swatiw; 08-28-2009 at 03:12 AM. |
|
|||
|
Re: testcase format, manual testing procedure
Quote:
In the case of stress test cases u can check the boundary length(characters length) && in the case of performance test cases u can check the time delay( time taken to shift from user name to passwd). All the test cases will cms under test plan . Thanks , Riju. Last edited by rijus; 08-28-2009 at 01:02 PM. |
|
|||
|
Re: testcase format, manual testing procedure
Hai friends,
Quote:
Thanks Deepa |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| manual testing procedure | rvija | Testing Issues | 18 | 1 Week Ago 06:30 AM |
| Manual Load Testing and Performance Testing | shyamsks1975 | LoadRunner | 1 | 05-18-2008 02:11 AM |
| Manual Testing | vsjprasath | Testing Issues | 4 | 02-14-2008 08:17 AM |
| Manual Testing | vsjprasath | Testing Issues | 3 | 02-14-2008 01:20 AM |
| Manual Testing | prasad79 | Testing Issues | 0 | 09-26-2007 04:20 AM |