Skip to main content

Structural Testing

Structural Testing is the type of testing in which user should have the knowledge of the code because in this testing user need to check the structure of the system. Structural Testing is White Box Testing.

The intension of  Structural Testing is not to check the input and generated output. Structural Testing intension have to check the internal structure of the software and check the various structure and data structure of the software.

In Structural Testing, tester need to know the show the software implemented and how the software is working. Structural Testing can be perform in all level of testing. Generally developers use this kind of testing in Component Testing and Component Integration Testing.

There are some techniques to cheek the Structural Testing
  • Statement Coverage: By using Statement Coverage we can identity that which Statement is executed and which code is not executed so we need to verify the every line to code to check the execution of statement. The main goal of this Statement Coverage to test the complete code with the minimum usage of Test Cases. Means in Statement Coverage we verify that how we can execute the complete code by using minimum number of Test Cases.
Formula to find the Statement Coverage

Statement Coverage = (Total Number of Statement exercised/ Total Number of Statement) * 100%

  • Branch Coverage: Branch Coverage is used to ensure that there should be a Test Case so that all Branches should be tested at least once. This is also called Decision Coverage. Branch Coverage we use when there are possibilities of two outcomes . It may be IF Statement , Do While Loop , Cases Statement because in all this 2 outcomes can come. One is True and other is False. So Branch Coverage say that each out come of control statement should be executed at least once. 

Formula for Branch Coverage

    Branch Coverage = (Total Number of Decision Outcome Executed/ Total Number of Decision Outcomes) * 100%

    • Path Coverage: In Path Coverage every possible path should be executed at least once . It means it cover all statement and branch at least once. 

    Formula for Path Coverage

      Path Coverage = (Total Number of Path Exercised/ Total Number of Path in the Program) * 100%

      Comments

      Popular posts from this blog

      Why Jmeter is best option for Performance Testing?

      There are multiple tools in market for performance testing of any software but Jmeter is the best solution among all of them due to some reason listed below 1) Jmeter is the open source application so users who use this application will not to pay anything. 2) You can use Jmeter for performance of any web application,  Databases and Web Services (REST and SOAP APIs). 3) Jmeter have the user friendly UI component so it is very easy to use. 4) Jmeter can be used to simulate to put maximum number of concurrent users on a server, network or object to test its strength or to analyze overall performance under different load types. 5) Jmeter also use for functional testing for static( JavaScript and HTML) and dynamic( JSP, Servlets and AJAX) resources. 6) Jmeter provides Verity of graphical representations for performance report so it is easy to understand.

      How You Can Test Database?

      Now we know the Database Testing which you can learn in my last article. In this article we will discuss about the steps that need to following to test any Database. Database Tester should have some basic knowledge regarding SQL Command like DDL (create/drop),  DML (Insert/Delete/Update) and DCL (Grant/Revoke).

      Causes of Software Defects

      It is practically impossible that developer develop a bug free software and that software we can deliver without Testing. If the complexity of the software increased then there must be bugs that can harm the users who will use that software.