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 — RustPython/extra_tests at main · RustPython/RustPython

Expand file tree

/

extra_tests

/
Copy path

Directory actions

More options

More options

Directory actions

More options

More options

Latest commit

 

History

History
History
/

extra_tests

/
Copy path

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
benchmarks
benchmarks
 
 
snippets
snippets
 
 
.gitignore
.gitignore
 
 
README.md
README.md
 
 
custom_text_test_runner.py
custom_text_test_runner.py
 
 
jsontests.py
jsontests.py
 
 
requirements.txt
requirements.txt
 
 
rustpython_wasi.sh
rustpython_wasi.sh
 
 
test_custom_text_test_runner.py
test_custom_text_test_runner.py
 
 
test_manager_fork_debug.py
test_manager_fork_debug.py
 
 
test_snippet_selection.py
test_snippet_selection.py
 
 
test_snippets.py
test_snippets.py
 
 

README.md

Outline

Test snippets

This directory contains two sets of test snippets which can be run in Python. The snippets/ directory contains functional tests, and the benchmarks/ directory contains snippets for use in benchmarking RustPython's performance.

Setup

Our testing depends on pytest, which you can install using pip.

Running

Simply run pytest -v in this directory, and the tests should run (and hopefully pass). If it hangs for a long time, that's because it's building RustPython in release mode, which should take less time than it would to run every test snippet with RustPython compiled in debug mode.

Regression result collector

jsontests.py uses the canonical regrtest process setup before discovery. Its JSON and tables count each parent test once; failed subtests make their parent fail. The standard unittest summary counts individual failure/error/skip events and can therefore differ. Each case retains its full id and all subtest callbacks reported by unittest, including their IDs, outcomes and tracebacks. Historical result files are not rewritten.

You are visitor 01402503 — 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.