We all know that testing your code is a critical step in deploying software, but manually following a script and pressing buttons on each screen is time consuming and error prone.In this class, we'll cover various testing strategies for Fusion 360 add-ins written in python, including structuring your add-in for unit testing, automating integration testing, and utilizing continuous integration systems.The goal of these is to ensure that your add-in is easily tested and verified, which will drive down bugs and drive up user satisfaction.This class is geared towards advanced programmers and add-in developers, and will cover Fusion 360 command and command definition APIs, events, and palettes.Experience with web development concepts (to use palettes) is highly recommended. (Joint AU/Forge DevCon class).
- Understand and choose appropriate testing strategies for your add-in
- Understand and use the Fusion 360 command APIs
- Learn how to use palettes to interact with Fusion 360 commands
- Learn how to use a continuous integration server to build, test, and package Fusion 360 add-ins
Jesse Rosalia is the founder of Bommer, and the developer of the Bommer for Autodesk Fusion 360 bill of materials manager.He has over 17 years experience in software development and architecture, including 2 years as the CTO of a small robotics startup (where he also dabbled in mechanical and electrical engineering), and is a mentor at the Highway1 hardware accelerator.Jesse is keenly interested in the intersection of hardware and software, particularly the use of software tools to aid in the hardware development process, and has a passion for building practical, useful, usable tools that delight and improve the lives of users everywhere.Jesse is a proud to be an alumnus of Georgia Tech, and lives in San Francisco with his wife and 2 cats.