Interface Fault Injection Guided by Artificial Intelligence

Method Purpose Short description of the method's purpose and main benefits

Interface fault injection guided by Artificial Intelligence, like its base method, is the injection of faults at the interface of components (OS calls, APIs, services…) through data corruption at interface level, with the purpose of evaluating the behaviour of the system or component under test in the presence of invalid inputs or stressful interface conditions. The novelty of this improved method relies on its usage of artificial intelligence to better accomplish the purpose of interface fault injection.

Method description A detailed description of the method

Interface fault injection guided by artificial intelligence also introduces erroneous input conditions at the interface of a system or component in order to evaluate its robustness and behaviour under invalid inputs. The addition of artificial intelligence solves the problem of defining which valid and invalid inputs should be used to maximize coverage and fault detection. Traditionally a pre-defined set of inputs has been used, which is based on realistic values, however artificial intelligence can dynamically create inputs (e.g., using genetic algorithms) that evolve and improve as the experiment execution goes on. Currently, an approach based on a Hillclimb-like search and using the OpenAPI specification of the service as input is being researched.

Method Strengths A listof the strengths of the method

Low effort required for the generation of robustness test cases
Easiness of use and integration of current tools
High coverage and fault detection ability through the usage of artificial intelligence

Method Limitations The limitations of the method

Classification of results is highly dependent on expert knowledge

Method References Bibliography references to papers about the method.

Method Dimensions

Evaluation Environment Type Type of environment where the method is applied. It can be more than one type of environment. (Dimension 1)

Evaluation Type Type of evaluation performed with that method. If a method is hybrid, more than one type can be selected. (Dimension 2)

Type of Component Under Evaluation Type of components that can be evaluated with that method. It can be more than one type. (Dimension 3)

Evaluation Stage The evaluation stage where the method is used. (Dimension 5)

Purpose of the Component Under Evaluation The type of purpose that can be evaluated by a method. It can be more than one type. (Dimension 6)

Type of Requirement Under Evaluation The type of requirements that a method is able to evaluate. It can be more than one type. (Dimension 7)

Evaluation Performance Indicator The type of evaluation criteria or KPI that a method is able to improve. It can be more than one type. (Dimension 8)

Relations

Related Methods A method could be related to other methods.

Tools A method can use zero or more tools.

Part Method A method (when it is a combination: Combination of method artefact that is a specialization of a V&V Method) could be composed of a set of V&V Methods.

Test Case or Verification and Validation activity Test Case or V&V activity performed in a Use Case. We will link to the method to the test cases where the method is used.

Standards A method can be linked with standards.

Context

Workflow

Contents

There are currently no items in this folder.