What methodologies used to develop test Cases?

  • Interview Candidate
  • 23
  • 2400

Showing Answers 1 - 23 of 23 Answers

Amali

  • Aug 4th, 2006
 

With the help of the scenarios involved in the functionality,testcases are written.

A test case document should contain;

1.Testcase id

2. Testdata.

3. Action to be done.

4.Status (i.e) whether that particular testcase have passed or failed.

  Was this answer useful?  Yes

amalijoyam

  • Aug 4th, 2006
 

Testcases will be written on the basis of the scenarios in an application.

Testcases should contain;

1.Testcase id

2. Testdata

3. Action to be done

4. Status (i.e) whether the executed testcase has been passed or not.

  Was this answer useful?  Yes

Shraddha

  • Aug 21st, 2006
 

1. Project Name

2. Module Name

3. Test case id

4. Funcation

5. Action

6. Expected/ Actual Result

7. Status Pass/ Fail

8. Created By

9. Date

  Was this answer useful?  Yes

bikram

  • Aug 23rd, 2006
 

1. Boundary value analysis

2. Equivalance partiotioning

  Was this answer useful?  Yes

prasad.gandra

  • Aug 30th, 2006
 

There is 3 types of test cases :

1) Business logic based test case design:( 80% will be covered in it ... functional cases) .... In this the fields are:

(a) Test case ID: (b) Test case Name : (c) Feature to be tested/Usecase ID : (d)Test suite ID: (e)Priotity ( p0,p1,p2) (f) Environment: (g) Effort (f) Duration (h) Test setup (i) Test procedure ( Step no.   ,   Action    , input required  ,  Out put expected    , Result   ) (j) Test case pass/fail criteria :

2) Input Domain based Test case design : ( 15 % will be covered in it ... input domain, error handling ).... in this fields are:

(a) object name

(b) Boundary value analysis : ( min & max ) contents will be in this

(c) Equivalance class partioning :  ( valid & invalid) contents will be in this .

3) User Interface test case design : ( 5 % will be coverage) : graphics check, spelling mistakes,meaning full error msgs and accuracy of data displayed and accuracy of the datain the database a result of user input , accuracy of the data into databse as a result of external factors, meaning full help  msgs with proper navigations.

  Was this answer useful?  Yes

S Rajesh Kumar

  • Sep 8th, 2006
 

Functional Test Cases
1. Equivalance Partition
2. Boundary Value Analysis
3. Error Guessing
Field Level Validations
Test Cases
UI Test Cases

  Was this answer useful?  Yes

PAWAN

  • Sep 29th, 2006
 

On the basis of these things we make a test cases1. Specifications2. On the basis of specifications we create a test scenarios3.on the basis of test scenarios we can create a test cases for each test scenarios. For making the test cases we can use boundary value analysis and equivalance partitioning on the basis of given specifications.example:--test the login screen1. Specification--username should be alpha numeric and length is 6 character minimumpassword--alphanumeric maximum 12 char and min 5 characters2. Username and password should be correct user name correct password incorrect3 input ---ab222222 password 4367567567----okinput ----f636664t password 2323---deny

  Was this answer useful?  Yes

sarada

  • Apr 4th, 2007
 

Suggested Methodology for Test Cases Review


Typically, reviews should be done during each phase in the Testing Life cycle. The phases involved in Software testing lifecycle are:


· Requirements understanding

· Test preparation

· Test Execution

· Test Reporting

  Was this answer useful?  Yes

Vani

  • May 25th, 2007
 

There are so many methodologies for developing test cases:

Equivalence partition  

Boundary value

Worst case conditions

Race conditions

State transition

traversal techniques

cause and effect


I feel these techniques cover almost all kind of practical scenarios.Anyone can add to this.

Thanks

  Was this answer useful?  Yes

kurtz182

  • Dec 28th, 2009
 

A TEST CASE DEVELOPMENT METHODOLOGY FOR SYSTEM TESTING

STEP ONE:  STUDY THE PRODUCT OR SERVICE
Learn everything that is relevant to testing about the product or service.  Do this in order to develop your test cases and create a test plan.

STEP TWO:  CONSIDER ALL POSSIBLE TESTS
Here are some things to think about to identify useful test cases:
1) explicit and implicit requirements
2) any fact-based claims that render true/false conclusions and are testable
2) how features or functions are integrated
3) program logic, business rules and work-flow
4) all of the possible values that can be input
5) equivalence class analysis and partitioning
6) testing at boundaries
7) constraints on input data
8) when the application is in different states
9) all of the paths throughout the application
10) things that enable the application to function and can be changed
11) things that consume some output of the application that can be changed
12) issues with concurrency; multiples users
13) various user roles and how these play out in the application
14) performance, load, and stress
15) international concerns
16) legal concerns


STEP THREE: SELECT MOST IMPORTANT TESTS AMONG THE POSSIBILITIES
Here are some things to think about when you consider which test cases to execute:
1) the time alloted for testing
2) your testing resources
3) the complexity of the project; duration of bugs fixes is often inversely proportional to the time afforded to testing (unless this is accurately factored into the equation during the planning stage)  
4) cost/benefit of tests found in STEP 1 in terms of risk and reward
5) where you are likely to find the most defects.
6) where you are likely to find the most severe and/or mission critical defects
 
STEP FOUR:  CREATE A PLAN
Document everything you intend to do throughout the entire test process.  Include things you intend to test as well as those you don't intend to test.  Then facilitate a meeting with relevant expert members who can provide useful feedback about your intentions.  They will often steer you in directions you hadn't considered.  Incorporate their feedback into your test plan, gain their approval, and baseline this document. 

STEP THREE:  AUTHOR TEST CASES
Just do it.

STEP FOUR:  MAP TEST CASES TO REQUIREMENTS
This will let you know whether all of the requirements are covered by test cases.

STEP FIVE:  PRIORITIZE TEST CASES
Among the test cases you chose to write, you need to categorize your test cases by importance in order to 1) know how issues should be handled if defects are discovered, and 2) choose the proper tests if there are reasons to restrict the test schedule.    

  Was this answer useful?  Yes

saravanan123

  • Jul 14th, 2010
 

there is no methodologies since once we read the requirement or undergoing with the application we should see where we can break the application for that how we can write based upon this methodology you can write the test case

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions