Skip to main content

kit_test

Lint & build PyPI version MIT license

A collection of test scripts for the Student Robotics v4 kit.

Tools

All scripts are subcommands of the kit_test entrypoint.

kit_test --help
kit_test <subcommand> [options]

For all the tests, adding the argument --log <log-location> will output all the test results to a CSV file.

power_v4

Here we are testing all outputs can be enabled and current sense is functioning. Additionally, we test the buzzer, LEDs and start button are functioning and finally we test both the software and hardware undervoltage protection.

To run this with an SRv4 Power Board power resistors matching the OUTPUT_RESISTANCE list in power_test.py need to be connected to each of the outputs and a power supply capable of providing 12 volts at 25 amps must be used. For the undervoltage tests, a Tenma 72-2545 power supply controller over USB is also required. Alongside this a changeover circuit is required to automatically switch the supply to the Tenma PSU when the output is enabled.

To run the test without the undervoltage tests, run:

kit_test power_v4

To run the test with the undervoltage tests, run:

kit_test power_v4 --test-uvlo

motor_v4

Here we are testing the both motor outputs function and that the current sensing is functional.

To run this with an SRv4 Motor Board connect power resistors to the motor outputs. The resistors must match the MOTOR_RESISTANCE value in motor_test.py in order for the test to function.

To run the test, run:

kit_test motor_v4

servo_v4

Here we are testing that all servo outputs are functional. Note however, that unless a separate 5 volt power supply is connected to auxiliary input, only the first 8 servos will move.

To run this with an SRv4 Servo Board connect servos to all outputs.

To run the test, run:

kit_test servo_v4

arduino

Here we are testing that all the pins on the arduino are functional.

To run this test you need to attach a testing hat to the Arduino that connects all pins (except pin 13) together through resistors and biases the common point to 2.5V.

To run the test, run:

kit_test arduino

If you wish to program up a different firmware you can provide the argument --stock-fw-hex with a path pointing to the compiled hex file of the firmware you want to flash.

When testing Arduinos that the mapping of asset code to serial number is not known add --collect-asset to also capture the asset code.

kit_test arduino --collect-asset

camera

Here we are testing that the camera is accessible and can capture undistorted images.

To run this, connect the webcam to test and point it at a test marker. The preview will freeze and highlight the marker when it is detected in the frame.

To run the test using an 80mm marker of id 101, run:

kit_test camera --marker-id 101 --marker-size 80

When testing cameras that the mapping of asset code to serial number is not known add --collect-asset to also capture the asset code.

kit_test camera --marker-id 101 --marker-size 80 --collect-asset

Inventory Helpers

Metadata

Release files for sr-kit-test 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sr-kit-test 1.0.0
File Size Uploaded
sr_kit_test-1.0.0.tar.gz 48.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for sr-kit-test 1.0.0
File Interpreter ABI Platform
sr_kit_test-1.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 104.5 kB

Release files / sr_kit_test-1.0.0.tar.gz

Download URL sr_kit_test-1.0.0.tar.gz
Size 48.1 kB
Tags Source
SHA-256 checksum
How to use checksums
400056c5bcd42336ab0c5ccfddb530c3c11def8d53416c41b61be04843bab671
BLAKE2b-256 checksum
How to use checksums
162cd6586de31899a3733456d0c693d13454baa574f27aa9bc94921bcabd7a2f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 22, 2025.

Transparency log

Release files / sr_kit_test-1.0.0-py3-none-any.whl

Download URL sr_kit_test-1.0.0-py3-none-any.whl
Size 56.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0b4f270fba8fc39a96d8f18c4a04263bed98f7d8dba8147909938eb2bf44fda5
BLAKE2b-256 checksum
How to use checksums
2d42afaddb900d5511c759b79e49f32a090675667fc146a9808f32301f359c97
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 22, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page