Such requirements are, by definition, non-functional [8]. Functional requirements by nature fall into category A in table 1 cannot be used for destructive testing. To incorporate mandatory destructive testing into nonfunctional requirements, clauses similar to the following have to be part of the requirements:. The software must be designed in such a way that proper behavior is obtained when the software is subject to improper usage or improper input.
No data shall be lost if the software prematurely terminates as a result of other system failures. The software shall not prematurely or unintentionally terminate as a result of any combination of user keyboard or mouse input. The software shall always produce proper output data regardless of the validity or correctness of input data. For specific software products, it is important to explicitly define the following and similar terms as used above:.
The author of this paper is currently working with a team to develop requirements specification for an example case study involving a data conversion program. The requirements being developed mandate the use of destructive testing as described above.
Subsequent to the completion of the requirements specification and implementation of the software, test cases will be developed for destructive testing of the software.
This work-in-progress paper has proposed a software testing paradigm destructive testing that deviates from conventional software testing. The goal of conventional software testing is to ensure a software product correctly performs all the functions specified in the requirements specification.
In contrast, the goal of destructive testing is to ensure a software product exhibits proper behavior when subject to improper usage or improper input. Ongoing work includes the development of requirements specification that mandates destructive testing of a case study software product.
Destructive testing does not replace conventional testing, rather, destructive testing supplements requires additional testing beyond conventional testing.
In other words, destructive testing is a reflection of the fact that, despite the best of intentions, a software user will sometimes use a software product in an improper manner.
Since destructive testing does not replace conventional testing, and it is performed in addition to conventional testing, destructive testing cannot be detrimental. It makes sure that application will work fine even if invalid inputs are provided to the application. It helps to identify the failure points if the application is misused. It is carried out under rigorous environment until the software breaks. To build a good destructive testing strategy, it is always good to have some knowledge of requirements although it does not require knowledge of all the system and application requirements.
Destructive Testing verifies the following things: Improper and proper software Behavior. Valid or invalid input data. Summary: Destructive testing is done to find out the point of failures which cannot be done using conventional system testing.
The application is made to break to check robustness. Done by QA team mainly. It focus on weakness in design but not functionality. Does not require any Business requirements. It helps to determine the service life of the product. It is performed under most severe operating conditions. Sign up just providing your email address below: Enter your email address: Check email in your inbox for confirmation to get latest updates Software Testing for free.
Related Articles. Table of Contents. Improve Article. Save Article. Like Article. Last Updated : 29 Apr, Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert.
Corroded pipes Fracture and mechanical testing Fracture and mechanical testing includes the following destructive tests: Bend test is a quality control test that bends materials either in a guided or free form test to expose embrittlement.
Charpy impact test is a high strain DT method that determines the amount of energy absorbed by a material during a fracture. Crush test or compressive strength test is a test widely used to determine the strength of concrete bearing loads. Weld fracture test is a test designed to reveal imperfections such as cracking due to inadequate width to height ratio, incomplete penetration, lack of fusion, porosity, and slag inclusion.
Peel and chisel test is a test that determines weld size and failure type. Pellini drop weight test is a test that determines the nil-ductility transition temperature NDTT. NDTT is the test temperature in explosion bulge tests at which the plate remains flat after a fracture and crack propagation occurs in the presence of elastic strains only. Hydrostatic pressure test is primarily an NDT method, but recently hydrostatic pressure tests have shown to exert strain within a material's elasticity, which only occurs micro structurally when the material being strained is slightly proportional to the pressure applied.
Fatigue testing Fatigue testing is conducted in salt water or open-air environments to determine the endurance of welded joints, base metals, and heat affected zones under variable- or constant-amplitude loading. Hardness Testing Hardness testing determines whether a component undergoes permanent deformation under stress using the Rockwell scale.
Hardness testing Source: Kimtaro, Dreamstime Hydrogen testing Hydrogen testing exposes a component at risk of corrosion to hydrogen at different strain rates and temperatures. Residual stress measurement Residual stress measurement measures the internal stress of a component and its effect on the surface stress. Here are three methods that can be used in residual stress measurement: Neutron diffraction Synchrotron diffraction X-ray diffraction Software testing Software testing is performed by software engineers who investigate the quality of the software, find failures, and understand risks before the product is fit for use.
Tensile elongation testing Tensile elongation testing i s a type of stress testing performed by elongating or compressing a component to determine the strength of the material. Tensile elongation test Torsion testing Torsion testing is a type of stress testing where twisting forces are applied to determine shearing of the material before it becomes deformed.
Examples of Destructive Testing Perhaps one of the most common examples of destructive testing is crash simulations. Table of contents. Share: f t n.
0コメント