Whether we write one test case for one use case?

Answers were Sorted based on User's Feedback



Whether we write one test case for one use case?..

Answer / ranjith nair

Some times "YES" and may times "NO"

Some usecases are very simple so that only one testcase is
required to cover the functionality.But many times usecases
are very complicated so that a lot ot testcases are
required tocover the whole functionality

ex"usecase->Applicant login the screen

This usecase needs a minumum of 10 testcases id to cover
the whole funcionality

Is This Answer Correct ?    6 Yes 0 No

Whether we write one test case for one use case?..

Answer / rao

I too agree with Ranjith.

Good...

Is This Answer Correct ?    0 Yes 0 No

Whether we write one test case for one use case?..

Answer / madan

A use case is a technique for documenting the potential
requirements from a software.They are otherwise called
Functional requirements. Each use case provides one or more
scenarios abt the functionalities of the Application that
convey how the system should interact with the end user or
another system to achieve a specific business goal. Use
cases enable a tester to write test cases much before the
coding.

Use cases can be simple to complex. may include single
functionality of the application to multiple
functionalities. so dependeing upon the functionality
coverage by the usecase, we may write either one test case
or multiple test cases.

Is This Answer Correct ?    0 Yes 0 No

Post New Answer

More Manual Testing Interview Questions

what comments have u given in peer review? tell me at least 3 comments what u have given? july27 brahma412@yahoo.co.in

2 Answers   CTS,


4. A software error can be described as: a. A description of the relationship between two or more variables or set members in which the value of one does not influence the values of others. b. Any ill-advised, substandard, or temporary fix applied to an urgent problem in the (often misguided) belief that doing so will keep a project moving forward. c. The process in which developers determine the root cause of a bug and identify possible fixes. d. A mismatch between the program and its specification. 5. Select a reason that does not agree with the fact that complete testing is impossible: a. The domain of possible inputs is too large to test. b. Limited financial resources. c. There are too many possible paths through the program to test. d. The user interface issues (and thus the design issues) are too complex to completely test.

1 Answers  


is there any openings in testing mba guys

1 Answers  


what is difference between test harness and test bed. Are they same? Plz reply.......

1 Answers  


how deployment phase of SDLC differs in product based and in service based company ?

0 Answers   TCS,






can any body explain what is Build intervel period.what are the main components in PDCS(projectdatacollectionsheet)

1 Answers  


3) What is PDCA Cycle?

4 Answers   Mind Tree, Scope International,


What r the input documents to the design test cases?

7 Answers   Covansys,


what kind of document are follow to write test case ??can u tell me briefly

3 Answers  


1. can u explain about testing levels and its type with example? 2. First explain about both testing.then difference B/W sanity and smoke testing? 3. Explain about integration , functional , system testing? 4. what are methods use to writing test cases?

2 Answers   Wipro,


what are the differences between stub abd the driver ?

5 Answers   CA, IIST,


What is system testing? What is defect leakage? What is penetration testing? What is regression testing?

4 Answers   RBS,


Categories