• DocumentCode
    2064102
  • Title

    Automated data flow testing

  • Author

    Dubey, Harsh Kumar ; Kumar, Prashant ; Singh, Rahul ; Yadav, Santosh K. ; Yadav, Rama Shankar

  • Author_Institution
    Dept. of Comput. Sci. & Eng., MNNIT, Allahabad, India
  • fYear
    2012
  • fDate
    16-18 March 2012
  • Firstpage
    1
  • Lastpage
    5
  • Abstract
    Testing is a process of executing a program with the intent of finding an error [7]. A good test is one that has a high probability of finding an as-yet-undiscovered error. A successful test is one that uncovers an as-yet-undiscovered error. Testing can be manual, automated, or a combination of both [6]. Manual testing of the software is inefficient and costly. If the testing process could be automated, the cost of developing software could be significantly reduced. There are mainly two strategies of testing, one is structural and other is functional. In structural testing the knowledge to the internal structure of the code is used to find the number of test cases [3] required to guarantee a given level of test coverage. For example data flow testing which selects paths of a program according to the locations of definition and uses of variables in the program. On the other hand, in functional testing, only observation of the output for certain input values is used as test cases. For example boundary value analysis [7]. So, in this paper we are focusing on one of the method of Structural testing called Data Flow Testing. For Data Flow Testing we have developed a tool which will automatically find the bugs in the program. Consequently, complexity and expected output of the program will be improved. The tool concentrates on the usage of variables and the focus points are: 1. Statements where variables receive values. 2. Statements where these values are used or referenced. As we know, variables are defined and referenced throughout the program. We may have few define/reference anomalies: 1. A variable is defined but not used/referenced. 2. A variable is used but never defined. 3. A variable is defined more than one time before it is used. These anomalies will be identified by static analysis of code i.e, analyzing code without executing it.
  • Keywords
    computational complexity; data flow analysis; program debugging; program testing; as-yet-undiscovered error; automated data flow testing; boundary value analysis; bug finding; define anomalies; functional testing; manual software testing; program complexity; program execution process; program expected output; program path selection; reference anomalies; software development cost; static analysis; structural testing; test cases; Computer science; Discrete Fourier transforms; Layout; Manuals; Software; Software testing; Data Flow Testing; Dc-path; Defining Node; Dupath; Line Number Generation; Usage Node; Variable Recognition;
  • fLanguage
    English
  • Publisher
    ieee
  • Conference_Titel
    Engineering and Systems (SCES), 2012 Students Conference on
  • Conference_Location
    Allahabad, Uttar Pradesh
  • Print_ISBN
    978-1-4673-0456-6
  • Type

    conf

  • DOI
    10.1109/SCES.2012.6199072
  • Filename
    6199072