Manual Tests

picoTracker Smoke Test Checklist

This document outlines a comprehensive set of smoke tests for verifying the core functionality of the picoTracker. These tests should be performed after significant changes to ensure basic functionality remains intact.

Usage Instructions

1. Run through each sections tests
2. Mark each test as passed (✓) or failed (✗)
3. Note any issues or observations in the test log, open any new issues on GitHub as required
4. For MIDI tests, ensure proper MIDI connections are established with TRS and USB
5. For audio tests, use appropriate monitoring equipment, be very careful when testing Line Level output!!

Projects

1. Boots into last loaded project

   • Verify project state is restored correctly
   • Check if playback position is maintained
   • Confirm all instruments and samples are loaded

2. Project Management

   • Create new project
   • Edit project name
   • Generate random name
   • Save project
   • Load "Tardline" project
   • Load "single cycles ac" project
   • Verify project metadata is saved/loaded correctly

Editing

1. Basic Creation

   • Create new chain
   • Create new phrase
   • Add notes
   • Create Sample instrument

2. Sample Management

   • Import sample into instrument
   • Verify sample properties (sample rate, bit depth)
   • Test different sample formats (WAV, AIFF)
   • Check sample normalization on import

3. Real-time Editing

   • Playback sequencer
   • While playing:
     • Edit instrument volume/pan
     • Adjust root note
     • Modify ADSR envelope
     • Change filter settings
     • Test instrument-specific parameters

Playback

1. Basic Playback

   • Play back "Tardline" project
   • Play back "single cycles ac" project
   • Test stop/start/continue
   • Verify tempo changes take effect immediately

2. UI Interaction During Playback

   • Navigate to mixer screen
   • Change channel volumes
   • Adjust master volume
   • Mute/solo channels
   • Test effect sends

3. Rendering

   • Render mixdown (full length)
   • Stop mixdown after 20s and verify partial render
   • Restart and render to end
   • Render stems (all channels)
   • Stop stem rendering after 20s
   • Restart and complete stem rendering

Device

1. Audio Output

   • Test HP Low & High (Headphone), Test Line out settings
   • Verify no clipping at maximum volume

2. Hardware Controls

   • Test all physical buttons
   • Test previous project reloaded on power off/on (allow autosave more than 60sec to save prev open project)

MIDI Functionality

1. MIDI Clock Sync

   • Test internal clock mode
   • Test sending external MIDI clock sync
   • Test sending MIDI start/stop/continue messages

2. MIDI Control

   • Test MIDI note input (upto 8 polyphonic)
   • Test receiving MIDI start/stop/continue messages

UI/UX

1. Screen Navigation

   • Test all screen transitions
   • Verify focus management between UI elements
   • Test key combos
   • Check context-sensitive help

2. Multicore Safety

   • Verify no UI freezes during heavy processing
   • Test rapid UI updates during playback (eg. mixer screen)

File Operations

1. Sample Management
   • Import multiple samples while staying in the import browser
   • Verify sample playback at different pitches
   • Check memory usage with large samples

Performance

1. CPU Usage
   • Check for audio dropouts with Tardline and SingleCyclesAc

Error Handling

1. File Operations
   • Test loading project with corrupted data file
   • Verify graceful handling of missing samples (assign a sample and then remove it from project samples subdir)