testbed_showcase

Contents:

• Tentacle
• octoprobe
• testbed_micropython
• testbed_showcase
  • Introduction
    • WIP Flightlevel: github
      • WIP: Trigger testrun by PR (Pull Requst)
      • WIP: Trigger testrun manually
      • WIP: Firmware build on Github
      • WIP: Firmware build by Octoprobe
    • Flightlevel: testbed
      • Specification of the testbed
        • Configure the tentacles
        • Configure of the testbed-instance
    • Flightlevel: pytest
      • pytest command line arguments
        • pytest_addoption()
        • Arguments –firmware
        • Arguments –firmware-build-url
      • pytest test collection
      • conftest.py
      • testbeds
    • Flightlevel: micropython
    • Flightlevel: hardware
  • Installation and Debugging
    • Installation Ubuntu
      • Installation: Users
      • Installation: APT
      • git clone testbed_showcase
      • python
      • Software requiring elevated access
      • Run your first tests
    • Installation Raspberry Pi 4
      • Prepare SD Card
      • First boot
      • Upgrade python 3.11.2 → 3.12.6
    • Debugging
    • Release testing
      • Testgroup octoprobe
      • Testgroup pytest
      • Testgroup Jupyter
  • Tutorial
    • Write tests
      • The bright side of Octoprobe/pytest
      • The dark side of Octoprobe/pytest
      • Why should I start with testbed_showcase
    • Write pytests
      • Setup and Teardown
        • Comments to above sequence diagram
        • References to to source code
    • Firmware under test
      • Download firmware under Test
      • Build firmware under Test
    • Debug on level pytest
      • Best practices for debugging
      • Debug pytest using the VSCode debugger
        • Use the VSCode pytest test explorer
        • Use the VSCode debugger
        • pytest will NOT enter the debugger, however, VSCode should
    • Debug on level micropython
    • Debug on level hardware
      • Strategy to track down hardware problems
        • Remove all tentacles which are not invovled
        • Verify the relays
        • Verify you python code using Thonny
        • Start moving micropython code into the test
    • Debugging tests
      • Debug on level pytest
        • Best practices for debugging
        • Debug pytest using the VSCode debugger
          • Use the VSCode pytest test explorer
          • Use the VSCode debugger
          • pytest will NOT enter the debugger, however, VSCode should
      • Debug on level micropython
      • Debug on level hardware
        • Strategy to track down hardware problems
          • Remove all tentacles which are not invovled
          • Verify the relays
          • Verify you python code using Thonny
          • Start moving micropython code into the test
  • Implementation
    • Design decisions
    • Specifiation of testbed_showcase
      • Signals
      • Tentacle roles
      • Features under Test
        • Feature under test FUT_TIMER
        • Feature under test FUT_I2C
        • Feature under test FUT_UART
        • Feature under test FUT_ONEWIRE
        • Feature under test FUT_I2C/FUT_UART/FUT_ONEWIRE: Communication errors
      • Tentacle DAQ_SALEAE
        • FUT implemented
        • WeActStudio DAQ
      • Tentacle DEVICE_POTPOURRY
        • FUT implemented
      • Tentacle MCU_LOLIN_C3_MINI
        • Pins assignements
      • Tentacle MCU_LOLIN_D1_MINI
        • Pins assignements
      • Tentacle MCU_PYBV11
        • Pins assignements
      • Tentacle MCU_RPI_PICO / MCU_RPI_PICO2
        • Pins assignements
      • Tentacles
        • Tentacle DAQ_SALEAE
          • FUT implemented
          • WeActStudio DAQ
        • Tentacle DEVICE_POTPOURRY
          • FUT implemented
        • Tentacle MCU_LOLIN_C3_MINI
          • Pins assignements
        • Tentacle MCU_LOLIN_D1_MINI
          • Pins assignements
        • Tentacle MCU_PYBV11
          • Pins assignements
        • Tentacle MCU_RPI_PICO / MCU_RPI_PICO2
          • Pins assignements
    • Signals
    • Tentacle roles
    • Features under Test
      • Feature under test FUT_TIMER
      • Feature under test FUT_I2C
      • Feature under test FUT_UART
      • Feature under test FUT_ONEWIRE
      • Feature under test FUT_I2C/FUT_UART/FUT_ONEWIRE: Communication errors
    • Tentacle DAQ_SALEAE
      • FUT implemented
      • WeActStudio DAQ
    • Tentacle DEVICE_POTPOURRY
      • FUT implemented
    • Tentacle MCU_LOLIN_C3_MINI
      • Pins assignements
    • Tentacle MCU_LOLIN_D1_MINI
      • Pins assignements
    • Tentacle MCU_PYBV11
      • Pins assignements
    • Tentacle MCU_RPI_PICO / MCU_RPI_PICO2
      • Pins assignements
    • Tentacles
      • Tentacle DAQ_SALEAE
        • FUT implemented
        • WeActStudio DAQ
      • Tentacle DEVICE_POTPOURRY
        • FUT implemented
      • Tentacle MCU_LOLIN_C3_MINI
        • Pins assignements
      • Tentacle MCU_LOLIN_D1_MINI
        • Pins assignements
      • Tentacle MCU_PYBV11
        • Pins assignements
      • Tentacle MCU_RPI_PICO / MCU_RPI_PICO2
        • Pins assignements
    • Testsbeds produced
      • Tentacles inventory
      • Delivery Inspection / Function check

Indices and tables

• Index

• Module Index

• Search Page