GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — circuitpython/tests at master · ProGamerCode/circuitpython

Expand file tree

/

tests

/
Copy path

Directory actions

More options

More options

Directory actions

More options

More options

Latest commit

 

History

History
History
 
 
/

tests

/
Copy path

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
basics
basics
 
 
bench
bench
 
 
circuitpython
circuitpython
 
 
cmdline
cmdline
 
 
cpydiff
cpydiff
 
 
extmod
extmod
 
 
feature_check
feature_check
 
 
float
float
 
 
import
import
 
 
inlineasm
inlineasm
 
 
io
io
 
 
jni
jni
 
 
micropython
micropython
 
 
misc
misc
 
 
net_hosted
net_hosted
 
 
net_inet
net_inet
 
 
pyb
pyb
 
 
pybnative
pybnative
 
 
stress
stress
 
 
thread
thread
 
 
unicode
unicode
 
 
unix
unix
 
 
wipy
wipy
 
 
README
README
 
 
pyboard.py
pyboard.py
 
 
run-bench-tests
run-bench-tests
 
 
run-tests
run-tests
 
 
run-tests-exp.py
run-tests-exp.py
 
 
run-tests-exp.sh
run-tests-exp.sh
 
 
skip_if.py
skip_if.py
 
 

README

This directory contains tests for various functionality areas of MicroPython.
To run all stable tests, run "run-tests" script in this directory.

Tests of capabilities not supported on all platforms should be written
to check for the capability being present. If it is not, the test
should merely output 'SKIP' followed by the line terminator, and call
sys.exit() to raise SystemExit, instead of attempting to test the
missing capability. The testing framework (run-tests in this
directory, test_main.c in qemu_arm) recognizes this as a skipped test.

There are a few features for which this mechanism cannot be used to
condition a test. The run-tests script uses small scripts in the
feature_check directory to check whether each such feature is present,
and skips the relevant tests if not.

When creating new tests, anything that relies on float support should go in the
float/ subdirectory.  Anything that relies on import x, where x is not a built-in
module, should go in the import/ subdirectory.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.