Re-boostrapped the package.
1 file changed
tree: 7c4fc655def8c630a5f5729c8bb2af25fd5a76f9
  1. .default-version
  2. .gitignore
  3. .travis.yml
  4. AUTHORS
  5. CHANGES
  6. CONTRIBUTING.md
  7. LICENSE
  8. Makefile-bootstrap
  9. Makefile.am
  10. Makefile.in
  11. README.md
  12. aclocal.m4
  13. bootstrap
  14. bootstrap-configure
  15. build/
  16. configure
  17. configure.ac
  18. doc/
  19. include/
  20. repos.conf
  21. src/
  22. tests/
  23. third_party/
README.md

Build Status Coverage Status

Nest Labs Fault Injection

Introduction

Nest Labs Fault Injection (nlfaultinjection) is designed to provide a simple, portable fault injection framework.

It should be capable of running on just about any system, no matter how constrained and depends only on the C Standard Library.

This is a simple framework that helps implement fault injection APIs. Fault injection APIs simplify the testing (manual or automated) of the error handling logic of individual components and whole systems; as a testing tool, a fault injection API is not as powerful as an extensive set of mock objects, but has the advantage of being able to run on a live system.

This is not an official Google product.

Getting Started

A SW module implements a fault-injection API by doing the following:

  1. Instantiate a FaultInjection::Manager object and define a list fault IDs; the Manager needs a name, storage for the configuration of the faults and the name of each fault; the Manager instance is the public API, through which another module of the system can configure faults (for example a test harness can turn on a fault by calling the FailAtFault() method). The module should also provide a public function that returns a C++ reference to the Manager and initializes the Manager the first time it is called.
  2. At the location in which the fault is to be injected, the nlFAULT_INJECT macro is used to inline code that if executed triggers a fault in the system; the macro queries the Manager object calling the CheckFault() method and executes the extra code if it returns true. The invocations of CheckFault are counted per faultID, which allows a test harness to automatically loop over different valid configurations.

Interact

There are numerous avenues for nlfaultinjection support: