latha

• Nov 7th, 2005

 

A use case is a description of how end-users will use a software code. It describes a task or a series of tasks that users will accomplish using the software, and includes the responses of the software to user actions. Use cases may be included in the Software Requirements Document (SRD) as a way of specifying the end-users' expected use of the software.

raghuramsuravarapu

 Profile Answers by raghuramsuravarapu Questions by raghuramsuravarapu

• Jun 13th, 2006

 

(1) Integration Testing :Testing of combined parts of an application to determine if they function together correctly.This testing can be performed in both black box and white box testing.The documents like SRS/Functional specifications/Use Cases/Work Flow can be used while deriving integration test cases.We will check the interaction between different units /different functions of an application/product.The format of test case will be almost same for any testing type/technique like test case number, Serial Number,Steps to perform,Test data,Expected,Actual,Status,Priority,Precondition,Created By,Created On,Executed By,Executed On.We have to divide the features /units where the interaction is possible in the application/product and start writing positive integration test case's and negative integration test cases.If there is any test data is needed can be derived from equvalence partitioning and boundary value analysis technique and specified in the test data coulmn in the test case.

(2)To track bugs from winrunner,we need to connect to test director or any defect tracking tool which it supports.From test director we can track the defects from status new to closed.

(3)Defects that are detected should be logged with New Status.After checking the bug the status of that defect changed to open and assigned to a programmer/developer.Developer fix the bug and assigns back to the tester with fixed status.Here the testing team will validate the defect to know that the defect that is fixed according to the developer is really fixed or not.If the defect is reproducible,it's status should be changed to fail and assigned back to the programmer/developer.If the defect is pass,change the status to closed.While validating the defect a tester will execute the test case where the defect is found.Still if there is any variation between expected and actual ,means defect is reproducible.

(4) Repairing a bug which is found is same as fixing the defect .To fix the defect,a developer will verify the priority and fix accordinlgly in serial order.For every defect ,he will try to reproduce again in developer's environment.If it is still reproducible,than he will check the code where the defect arises and by his knowledge on the code,he will change the code according to the requirements.

pavanswapna

 Profile Answers by pavanswapna 

• Sep 15th, 2006

 

3.how u customise the bugs as pass/fail

Execute the Test Cases according to the functionality.If there is any difference between Expected Result and Actual output then it is called as a bug else when the requirments are not satisfied it is called as bug

4.u find a bug how will u repair
When a bug is found, log the bug in the Defect Tracker with status of the bug as 'Open' and assign to Developers.

5.in testcases u have bug or not

If Expected Result and actual output is same then the Test case is pass else fail

6. what is use case ? what it contains

I think use case is Design document or flowchart(whih looks like a diagram). it helps to understand the functionality of the application.