tINI-test 0.5.0__tar.gz

tini_test-0.5.0/.gitignore

@@ -0,0 +1,230 @@
+# 1127 tests with source
+test_stress
+test_stress_copy
+test_stress_copy_1
+test_stress_copy_2
+test_stress_copy_3
+test_stress_copy_4
+test_stress_copy_5
+test_stress_copy_6
+
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+*.lcov
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi/*
+!.pixi/config.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule*
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml

tini_test-0.5.0/.python-version

@@ -0,0 +1 @@
+3.13

tini_test-0.5.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) [2026] [Aggelos Arelakis]
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

tini_test-0.5.0/PKG-INFO

@@ -0,0 +1,266 @@
+Metadata-Version: 2.4
+Name: tINI-test
+Version: 0.5.0
+Summary: A small library/framework used for testing your python source code.
+Project-URL: Homepage, https://github.com/AggelosAr/tini_test
+Author-email: Aggelos Arelakis <aggelosarelakis@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# tINI test
+
+A lightweight Python test framework focused on simple test discovery and execution from the command line.
+The framework was tested using its own test suite and has 100% coverage. It was also stress tested on around 1K tests to test db connections on a temp sqlite3. It also allows pretty prints inside the tests while running.
+
+## Installation
+
+```bash
+pip install tini_test
+```
+
+## Usage
+
+```bash
+python3 -m tini_test [-r RUN MODE] [-v VERBOSITY] [-d DIRECTORY] [-f FILE] [-t TEST] [-h HELP]
+```
+
+---
+
+## Filter Combination Behavior
+
+Filters are applied from broadest to narrowest scope:
+
+1. Discover tests within `-d` (if provided)
+2. Restrict to `-f` (if provided)
+3. Restrict to `-t` (if provided)
+* If used alone, the entire project is scanned.
+* Options may be combined in any way.
+
+---
+
+## Test Registration
+
+```python
+@Test.case
+def test_cats() -> None:
+    ...
+
+@Test.case()
+def snakes() -> None:
+    ...
+```
+
+The decorator accepts up to two optional callables.
+
+
+```python
+@Test.case(
+    lambda: create_database(),
+    lambda: destroy_database()
+)
+def test_database() -> None:
+    ...
+
+@Test.case(setup, lambda: destr())
+def test_database() -> None:
+    ...
+```
+
+
+
+### Catch exceptions
+
+```python
+@Test.case
+def test_math() -> None:
+
+    with WillRaise(NameError, ZeroDivisionError):   
+        1/0
+```
+Notes: If one of the provided exceptions is not raised the test will fail and raise an `ExceptionWasNotRaised` error.
+
+### Comparisons
+
+```python
+@Test.case
+def test_list_values() -> None:
+
+    expected = [12345]
+    must_equal(expected, some_func())
+```
+
+### Combo
+
+```python
+@Test.case
+def test_ints_dont_match() -> None:
+    a = 10
+    b = 20
+
+    with WillRaise(_IntegerMismatchError) as context: 
+        must_equal(a, b)
+
+    must_equal('10 != 20', str(context.exception))
+
+```
+
+
+### Misc
+
+When comparing custom objects the test suite will try to autocompare them but it is better to be explicit and pass them a callable that will apply the correct comparison.
+
+```python
+@Test.case
+def test_must_equal_alien_object_with_eq() -> None:
+
+    expected = A(11)
+    actual = A(21)
+
+    comp_func = lambda a, b: a.attr == b.attr
+
+    must_equal(expected, actual, comp_func)
+
+```
+
+## Test Discovery
+
+The requested path is resolved relative to the current working directory.
+
+A file is considered discoverable when:
+
+* The file name begins with `test_`
+* The file exists inside a directory named `tests`
+
+
+
+
+### Flow
+
+- Setup is executed before the test function runs.
+
+
+- Cleanup is executed after the test function completes.
+
+- Cleanup execution is still attempted when setup or test execution fails.
+
+- Maybe further down the road this will be made optional by a flag.
+
+---
+
+### Run modes
+Currently there are two modes *_sync_* amd *_async_*.
+In _sync_ mode all tests run in sequential and in _async_ they run concurrently.
+```bash
+tini_test -r sync
+```
+
+---
+
+### `-d DIRECTORY`
+
+Limit test discovery to a specific directory.
+
+```bash
+tini_test -d test_math
+```
+
+All tests in the `test_math` dir will run.
+
+
+---
+
+### `-f FILE`
+
+Limit execution to tests contained in a specific file.
+
+
+```bash
+python3 -m tini_test -f test_concurrency
+python3 -m tini_test -f test_concurrency.py
+```
+
+
+Notes:
+If multiple files with same name exist in different directories all will run.
+
+
+---
+
+### `-t TEST`
+
+Run a specific test function.
+
+
+```bash
+python3 -m tini_test -t function_name
+```
+
+
+Notes:
+If multiple functions with the same name are defined in different files only the first one spotted will run.
+
+---
+
+
+
+## Verbosity Modes
+
+### NORMAL
+
+Displays:
+
+* Captured IO in the correct order
+* Setup execution (if any)
+* Test execution (if any)
+* Cleanup execution (if any)
+* Full exception details
+* Stack traces
+* Test discovery information
+* Final summary stats
+---
+
+### SORT
+
+Works the same way as normal. But failures are sorted to the bottom.
+
+The sorting is only applied per module . 
+
+*Maybe further down the road a flag to sort globally may be introduced.
+
+---
+
+### MINIMAL
+
+Minimal display:
+
+* Failed tests ( names only )
+* Associated stack traces
+* Final execution summary
+
+
+`MINIMAL_NO_STACK` is same as `MINIMAL`, except that no stack traces are shown.
+`SUPER_MINIMAL` is same as `MINIMAL_NO_STACK` but less verbose.
+
+---
+
+
+## Notes
+
+
+While the discovery implementation will find tests with the same names or sub dirs with same names or even actual tests cases with same names, it is heavily discouraged.
+
+Of course the above is somewhat cancelled because the algorithm tries to autocomplete the path, as a result when searching for a sub directory that exists in multiple sub directories with the same name, no guarantees are made that all tests will be excecuted.
+
+
+---
+
+
+## Roadmap
+
+* [ ] Register tests into groups (group-level setup/cleanup)
+* [ ] Add global fail sort mode, not just per module.
+* [ ] Add exclude dir arg