Community
Join the OpenHTF community to collaborate with fellow hardware and manufacturing test engineers, get support, and share knowledge.
Join our Discord server to get help and collaborate with fellow hardware and manufacturing test engineers.
Read the documentation, ask questions on the Discord server and get answers from other test engineers using OpenHTF. Errors or gaps in the docs are fixed through issues and pull requests on the openhtf-docs GitHub repository.
- Read the docsopenhtf.com
- Ask on Discordquestions, setups, bugs
- Get an answerfrom test engineers using OpenHTF
- Open an issuetofupilot/openhtf-docs
- Pull request mergeddocs updated for everyone
Whether you're new to OpenHTF or a pro, our team and community is here to support you.
Disclaimer
This documentation is not affiliated with or endorsed by Google. It is provided by independent contributors to help users of OpenHTF. All information is based on our own experience and is offered as-is, without any guarantees.
Contribute
This documentation is open-source, just like the framework. If you find an error or notice something missing, feel free to open an issue on the documentation's GitHub repository. You can also reach out to us on Discord or via email.
About us
We're robotics manufacturing test engineers using OpenHTF. The lack of documentation slowed us down, so we created our own to help others. Then we went further and built TofuPilot—a plug-and-play database and analytics tool for manufacturing tests. It works seamlessly with OpenHTF, saving your team a lot of time.
OpenHTF today
OpenHTF has been a key tool for our team. Unsure about its current maintenance and future, we visited its founders, John and Joe, in Mountain View, and spoke with Akash, who now leads its maintenance at Waymo. We learned that OpenHTF is actively maintained by a dedicated team of five engineers, with no internal forks or breaking changes expected.
