How can we write testcases from Requirements..?Do the Requirements represent exact Functionality of AUT

  • Interview Candidate
  • 14
  • 6069

Showing Answers 1 - 14 of 14 Answers

sabir

  • Jan 20th, 2006
 

it is true that when ever we speak about the testing we say that testing strats from the reqiurment analysis so we should able to write the test case for the reqirement say ur developing a appliacation for whidh is developed for the accuontig then we are see that all reqirment that s/w taken or not file:///usr/share/doc/HTML/index.htmlfile:///usr/share/doc/HTML/index.html

  Was this answer useful?  Yes

Brahmesh

  • Jan 21st, 2006
 

Yes, Requirements should represent exact functionality of AUT.

First of all you have to analyse the requirement very throughly in terms of functionality. Then you have to think about suitable testcase design techniques (Black Box design techniques like Equivalance Partitioning, Boundry Value Analysis, Error Guessing and Cause Effect Graphing) for writing the testcase.

By these concepts you should write a testcase which should have the capability of finding the absence of defects.

  Was this answer useful?  Yes

venkat

  • May 29th, 2006
 

Hi,

 Test case preparation will be made by using Test scenarios.

Test scenarios are prepared by using Test plan ( H L D, L L D).

The hierarchy will follow like this

Test Plan

Test Scenarios

Test Cases ( Positive Case, Neagative case)

Regards,

Venkat

  Was this answer useful?  Yes

sanjay

  • May 30th, 2006
 

What is the right way to test cases for the following ............

                                 if we have only two options login name and password with ok and cancel buttons.............plz tell me detail how to write test cases for it.

  Was this answer useful?  Yes

rameshk

  • Jun 27th, 2006
 

What does Test scenarios consists of that is being used to write test cases.

  Was this answer useful?  Yes

mo_le

  • Jun 30th, 2006
 

To answer the question of how to write a test case for a simple window.

Try to identify the text boxes and commands of the window, then test for boundry, text, type of field (like password would be different than a regular field).

Then, test the buttons and the functionality you would expect to happen after clicking that (like: if you click OK on a login window, behind the screen a validation will happen and if the user and password are correct, you would be granted a successfull entry, etc....)

Try also to validate what happens when you click on the cancel button.

  Was this answer useful?  Yes

Pradeep

  • Jul 5th, 2006
 

Hi !

Scenarios gives you a picture of what to test. This is like a condition and more over like Use Cases. Depending on scenarios you write test cases.

Scenario >> Test Cases.

Ex: Test Item : Pen

Scenario 1: How ink flow (pen) works in Summer ( Temp High)

Scenario 2: How ink flow (pen) works in Winter ( Temp low)

For these scenarios you can write test cases .

  Was this answer useful?  Yes

rajani

  • Aug 16th, 2006
 

Hi soumya,.. what is AUT in ur question? Please let me know that!!

  Was this answer useful?  Yes

Arghya

  • Sep 25th, 2006
 

AUT is Application Under Test.

Yes we start writing test cases from the Requirements of the application.Once the use cases are designed,we can identify the different test scenarios and write test cases for those scenarios. 

  Was this answer useful?  Yes

sushmitha

  • Dec 1st, 2006
 

 Here AUT means Application under test i.e the application we are testing

  Was this answer useful?  Yes

santosh sunkoji

  • Dec 5th, 2006
 

Yes, we start writing the test cases with respect requirment specifications and based on usecases

  Was this answer useful?  Yes

abhishektuppada

  • Oct 15th, 2007
 

Well I would slightly differ from all the others, As per my knowledge the Test Cases are to be written based on the Business Requirements & not the Use Cases. Writing Test cases based on the Use Case would be process non-confirmance on a CMM Level-5.

Tester's job is to basically validate the software against the business requirements of the Client & not Use case. He should be able to map the requirements to the Test Cases designned & tested in the Tracebility Matrix.

  Was this answer useful?  Yes

kurtz182

  • Jan 5th, 2010
 

I think you've got it backwards:  The application under test (AUT) must represent the exact requirements. 

To answer your first question, the requirements are authored by someone in the business sector who has worked closely with customers or client to bring together everything that has been disclosed to fulfill what the customer requires.  These requirements are typically written in the form of use cases-- narratives that describe how the system is to be used from a customer-centric perspective.  Each use case is broken down into individually testable functionalities.  If the functionality is complex, it is a good idea to create a work-flow diagram or activity diagram and let the author of the use case review it for accuracy.  This diagram will illustrate the various paths that will need to be tested. 

Remember, the requirements don't cover all of your tests cases.  You may also need to create test cases from the specifications as well.

  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