Getting Started Guide

Getting Started Guide#

Introduction#

This document presents a guide for getting started with Fuze™ Test. Fuze™ Test is an 4TLAS enterprise-level framework for the control, execution, and management of automated testing for bembedded systems. CSL ATF functions are as follows:

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

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

  • Preparing test content to be executed on the target host machine(s)

  • Coordinating test case execution across the DUT farm

  • Organizing and presenting results of a test cycle

Fuze™ Test is designed to be a “person in the lab.” Therefore, its feature set, functionality, interfaces, and test content presentations are as if you are the one peforming the operations. Fuze™ Test uses the tools and local or networked cloud DUT setups that you currently use.

The primary, intended usage of Fuze™ Test is fully automated testing associated with CI, time-based, or release event triggers. However, Fuze™ Test can also be used for partially automated workflows performed with human orchestration. This allows both informal and formal testing to take place using a consistent method, eliminating multiple points of development and maintenance 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, and formal QA testing.

Note

This guide assumes you are executing on a Windows-based machine due to existing tools being implemented for Windows. 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 an Fuze™ Test user becomes more familiar with the details through frequent usage, this material is not needed as frequently.

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