<commit_before>**DISCLAIMER:** This is not an official Google product.

##[![Build Status](https://travis-ci.org/amyxchen/openhtf.svg)](https://travis-ci.org/amyxchen/openhtf)
[![Build Status](https://travis-ci.org/amyxchen/openhtf.svg?branch=refactor)](https://travis-ci.org/amyxchen/openhtf)
# OpenHTF
The open-source hardware testing framework.


## Design Philosophy
OpenHTF is designed to abstract away nearly all boiler plate of hardware test
setup and execution, so test engineers can focus entirely on writing actual
tests. It aspires to do so in the most lightweight and minimalistic way
possible. It is general enough to be useful in a variety of hardware testing
scenarios, from the lab bench to the manufacturing floor.


## Duties of a Hardware Testing Framework
OpenHTF attempts to distill the core duties any hardware testing framework must
perform, handle each one in a clean, sensible fashion, and avoid any additional
fluff. Those duties are (with example tasks):

  * Manage configuration for each test.
    * e.g. Load calibration data from a configuration file.
    * e.g. Use a configuration file to point testers to networked test
      equipment.
  * Provide consistent testrun I/O.<commit_msg> README.md change for status icon<commit_after>**DISCLAIMER:** This is not an official Google product.

[![Build Status](https://travis-ci.org/amyxchen/openhtf.svg?branch=refactor)](https://travis-ci.org/amyxchen/openhtf)
# OpenHTF
The open-source hardware testing framework.


## Design Philosophy
OpenHTF is designed to abstract away nearly all boiler plate of hardware test
setup and execution, so test engineers can focus entirely on writing actual
tests. It aspires to do so in the most lightweight and minimalistic way
possible. It is general enough to be useful in a variety of hardware testing
scenarios, from the lab bench to the manufacturing floor.


## Duties of a Hardware Testing Framework
OpenHTF attempts to distill the core duties any hardware testing framework must
perform, handle each one in a clean, sensible fashion, and avoid any additional
fluff. Those duties are (with example tasks):

  * Manage configuration for each test.
    * e.g. Load calibration data from a configuration file.
    * e.g. Use a configuration file to point testers to networked test
      equipment.
  * Provide consistent testrun I/O.
{'fraction_non_alphanumeric': 0.06845238095238096, 'fraction_numerical': 0.0, 'mean_word_length': 4.4467592592592595, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 6, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '584328', 'n_tokens_mistral': 641, 'n_tokens_neox': 619, 'n_words': 298}