How will you write test cases for a code currently under development?

  • Interview Candidate
  • 71
  • 6718

Showing Answers 1 - 71 of 71 Answers

Deva

  • Jun 8th, 2005
 

This is very common for testing of new features. A BRD (Business Requirement Document) will be used as the primary document to write the test cases. In some complex feature implementation we may need to refer the Technical Design Document from Developers too.

Deepak.Bhandarkar

  • Jun 8th, 2005
 

It will depend on the Requirements Specifications and depends on the SRS (Software Requirements Specifications) and Test Plans.

  Was this answer useful?  Yes

srija_goli

  • Jun 9th, 2005
 

the test case smay be written by the clear understand of the documents like srs,brs,frs prepared after the analysis of the raw info got from the customerand then they can prepare the test cases by seeing those documeants

  Was this answer useful?  Yes

Subash Chandar

  • Jun 10th, 2005
 

The test case is prepared by using the use cases and the srs docs

  Was this answer useful?  Yes

Kumar Amit

  • Jul 21st, 2005
 

The test case can be prepared by using SRS, Design Documnet, Use Cases and referring Activity diagrams of the functionality

  Was this answer useful?  Yes

BALA CHANDER .C

  • Jul 25th, 2005
 

IT ALL DEPENDS ON THE SRS(SOFTWARE REQUIREMENTS SPECIFICATION) GIVEN BY THE CLIENT. SINCE THE CLIENT SATISFACTION IS VERY IMPORTANT IN ANY PROJECT 

Siddik Shaik

  • Sep 1st, 2005
 

If the code is under development stage or after the development stage or what ever may be the stage, the test cases should be prepared before coding start. 
 
So, test case written must be depends on the requirements given (FDD, TDD or SRS), based on the functionality of the application. 

  Was this answer useful?  Yes

swapna

  • Sep 12th, 2005
 

it totally depend on functional design document, technical design document or SRS.

  Was this answer useful?  Yes

Radhika

  • Sep 25th, 2005
 

You can start writing the test cases following the SRS (Software Requirements Specification). The developers will start writing the code seeing the SRS and testers will start writing their test cases using the SRS.

  Was this answer useful?  Yes

Mohit

  • Oct 13th, 2005
 

when the requirements are given to a developer,a tester can participate in that Requirement understanding round and after a brief dicussion with team members,a tester can write testcases for the application under implementation stage using Exploratory Testing.

gopi

  • Oct 14th, 2005
 

The First Thing I will go through the Requirments if it is not understandable then we will conduct Requirment Analysis within our Team, then if need we will get the knowledge on the product from the developers.

after that i will Prepare Requirement Traceblity Matrix, Then Preparing Test Cases .

  Was this answer useful?  Yes

Taps

  • Feb 8th, 2007
 

The best way to write test cases for a code currently under development could be:
1. From the SRS document
2. From the IADs (Information Architect Document)
3. From the use cases
4. From the build manifest
5. From the Base line document (from which developer prepare HLD, LLD or start coding the reqiurement )

  Was this answer useful?  Yes

suresh

  • Apr 8th, 2007
 

please tell me what is Information Architect Document

  Was this answer useful?  Yes

saransh

  • Jun 21st, 2007
 

Test cases are basically based on SRS, BRS, and FRS but if any project is under development then there is need to know how many functions are completed and write test acording to them first.

  Was this answer useful?  Yes

murali

  • Jul 13th, 2007
 

The test cases are prepared based upon the SRS document not upon the coding.
This takes place simultaneously

  Was this answer useful?  Yes

Mohan Murali Velpuri

  • Jul 26th, 2007
 

Let me explain clearly:


Development Team and Testing Team receive the same BRS and SRS Documents.  Developers use these documents and go-ahead with there part of the job(Analysis, Design, Coding, Unit Testing and Integration Testing). 


On the other hand Testers Use these documents and go-ahead with there part of the job(Writing UseCases, Writing TestCases and Preparing Traceability Matrix.) 


Once the Developers release the Build, Testers use their TestCases to Test the Application Build.  


So there is no relation as such on the TestCases Preparation due to coding as these jobs are carried separately by two different Teams.



All the best.
Bye
Mohan


Jerome Rozario

  • Oct 19th, 2007
 

For a code currently under development, We can write test case using SRS or FRS.

  Was this answer useful?  Yes

amit raj

  • Nov 21st, 2007
 

Hi srija,
It is the part of static testing.In which we dont have the developed code.we follow the BRS,SRS Or FRS.
actually we all follow a process in the testing.LIK---

BUG PREVENTION------------>BUG DETECTION---------------->BUG RESOLUTION(developer)


In Bug prevention we FOLLOW the analyse part or can developer help,can Take BRS ,srs,frs.
we assume all aspects those may arrises.after that we  detect the  bug in the application.and check this to our bug prevention report.
we can take the help of traceblity metrix also.

  Was this answer useful?  Yes

kiran2geek

  • Jan 16th, 2008
 

Once its given BDD,FRS,FDD,SRS from customers and after analysis of the document testcases prepared based on mentioned documents.

  Was this answer useful?  Yes

saransh.kanaujia

  • Mar 20th, 2008
 

We can start writting test cases with the help of srs. generally testing team is involve from requirment analysis. So it's not new practice to write test cases when project is under development. unit testing and integreted testing is done when project is under developmen. It is  a step of testing going to white box testing toward's black box testing

  Was this answer useful?  Yes

s.subashnayak

  • Jun 22nd, 2008
 

Test cases are written according to the SRS so I can write the test cases for the under development code according to the SRS because code also developed to meant the features according to the SRS.

  Was this answer useful?  Yes

surendra_kumar

  • Jun 23rd, 2008
 

no need to write the test cases for the code which is under development. Infact anybody can write the test case for the application which is developed.

my suggestion for you is Learn to ask the question first, the question itself should be clear enough to answer.your question seems to be too immature.

  Was this answer useful?  Yes

StevenPace

  • Jul 12th, 2008
 

Ideally, the test case should be somewhat independent of the actual code, it should be useful for testing ANY program the performs the function, or has a simular function.  Performance limits would certainly change, you would have to fill them in later, or change the test case as the program changes. 

  Was this answer useful?  Yes

StevenPace

  • Jul 12th, 2008
 

Writing cases from specifications is good in theory, and I am sure that is appropriate in the developement of mission critical system.  But since I have worked on normal consumber software,  I have never seen a specification that is at all useful.  They are unreadable, have no details, have contradictions, and the bugs that you report on them are ignored.

  Was this answer useful?  Yes

pallavi.online

  • Aug 25th, 2009
 

When a development starts writing a code they have some requirement document with them and based on that they develop FDD and HLD.
Similarly,testers have same requirement document and based on it they prepare there test cases.
And through test cases they test the funtionality.

  Was this answer useful?  Yes

kurtz182

  • Dec 16th, 2009
 

Writing test cases for code currently under development is a natural process in the software and testing development life cycles.  Both activities are typically performed simultaneious and in parallel.

  Was this answer useful?  Yes

Umashankar

  • Dec 19th, 2011
 

HLD - High Level Design & LLD - Low Level Design

  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