Getting Started Guide

Getting Started Guide#

Introduction#

This document presents a guide for getting started with Fuze™ Test, the 4TLAS enterprise-level framework for controlling, executing, and managing automated embedded systems test. Fuze™ Test functions are as follows:

  • Initializing Device(s) Under Test (DUTs), including peripheral control systems and mechanisms

  • Deploying software and test content to the DUT’s connected host machine

  • Preparing test content for execution on the target DUT (via its connect host machine)

  • Coordinating parallel test case execution across an N > 1 DUT farm

  • Collecting, organizing, and presenting a test cycle’s results

Fuze™ Test is designed to act as a “person in the lab.” Therefore, its feature set, functionality, interfaces, and test content presentations replicate as close as possible a person peforming the test. This allows a human to easily craft and understand test content. This also supports a progression that allows intelligent agent(s) to learn the same.

Fuze™ Test uses the tools and (local or networked/cloud based) DUT configurations and instances that you currently use, supporting easy adoption.

The primary, intended usage of Fuze™ Test is fully automated testing associated with CI, time-based, or release event triggers. This is the greatest “value add” scenario. However, Fuze™ Test also enables partially automated workflows performed with human orchestration. This allows both informal and formal testing to take place using a consistent method, eliminating multiple development and maintenance points across your software/firmware automated test activities. Examples of automated test activities using Fuze™ Test can, therefore, include:

  • Prototyping new test cases and Fuze™ Test features

  • Software/firmware unit testing

  • Formal QA testing

Note

This guide assumes you are executing on a Linux-based machine. However, the Fuze™ Test is designed to be executed on either Windows or Linux-based platforms, so certain aspects may need to be adjusted for your platform as needed (e.g., path separators).

First Time Readers#

If this is your first time reading this document, it is recommended that you read through all the material in the order presented.

However, if you are only interested in quickly getting up and running with Fuze™ Test in your local environment, please refer to the Tutorial: Quick Start Guide page.

The material is presented in two main sections. The first main section describes the general Fuze™ Test test cycle sequence of activities from a tester’s perspective. The second main section provides more detail on each activity. The expectation is that as a Fuze™ Test user (or intelligent agent) becomes more familiar with the details through frequent usage, this material is not needed as frequently.

The root repository folder is named atf/. For simplicity, all references to “atf" folders omit the parent directory structure resulting from either cloning the Fuze™ Test repository (for development activities) or downloading and extracting the Fuze™ Test package (for formal testing activities).

TBD

Contents