Skip to Content
DocumentationPython ScriptingGuidesTesting Scripts

Testing Scripts in Brender Cloud

This guide explains how to safely test Python scripts in Brender Cloud’s CPU-based environment before running production jobs on GPU instances. Test executions are free and designed to catch errors early.

Uploading Scripts

  1. Navigate to Scripts Dashboard 
  2. Click Upload button (top-right corner)
  3. In the upload dialog:
    • Select your Python script file
    • (Optional) Add description for team context
Python script upload dialog

Managing Scripts

After upload, scripts appear in your studio’s script table. All members can:

  • View/Edit Code: Click any script row to access detail view
  • Modify Directly: Use built-in editor in script detail view
  • Delete: Remove scripts no longer needed

Running Tests

  1. From script detail view (https://brendercloud.com/scripts/your-script-name/test), click Test Script
  2. In test configuration:
    • Upload .blend or .zip file (max 15MB)
    • Click Run Test
Script test configuration

Tests execute immediately but may take 1-5 minutes depending on complexity

Test Environment Specifications

ParameterSpecification
Runtime Limit5 minutes maximum
HardwareCPU-only environment
Output GenerationNo files saved
Supported EnginesCycles (EEVEE not supported)

Understanding Test Results

After execution, you’ll receive:

Python script test output
  1. Console output from script execution
  2. Error stack trace (if any)
  3. Memory/Runtime metrics
  4. Virtual file structure printout using BC_OUTPUT_FOLDER
# Example debug print in test mode
print("Output path structure:", os.listdir(BC_OUTPUT_FOLDER))
⚠️

Test mode disables actual file writes. Use print statements to verify file paths and data flow.

Best Practices

  1. Small Assets: Use low-poly test models under 15MB
  2. Quick Checks: Focus on critical functions rather than full renders
  3. Debug Outputs: Use print() statements liberally
Last updated on
Environment VariablesSingle Server