mirror of
https://github.com/pre-commit/pre-commit-hooks.git
synced 2026-04-06 03:56:54 +00:00
deleted unnecessary manual testing files an folders
This commit is contained in:
parent
8e79502b8a
commit
bc7315b861
60 changed files with 1 additions and 1450 deletions
|
|
@ -4,12 +4,3 @@ ALL pre_commit_hooks tests, not only Loaderon's):
|
|||
coverage erase
|
||||
coverage run --source pre_commit_hooks -m pytest
|
||||
coverage report
|
||||
|
||||
#######################################################################################################################
|
||||
|
||||
Each automatic test method should have three stages:
|
||||
-Initialization: declaring and specification of all necessary variables and data for the test.
|
||||
-Execution: run all to-be-tested procedures.
|
||||
-Restoration: Eventual undoing of actions that may have changed external configurations. So as to ensure unit testing
|
||||
isolation. Restoration should go before verification in case test fails.
|
||||
-Verification: checking of obtained results. Might not be necessary when an exception is expected.
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
Inside pre_commit_hooks/loaderon_hooks/tests/manual_testing you can find several finds which function is to allow
|
||||
quick manual testing of any developed hook.
|
||||
|
||||
runner.py is in charge of calling the main function of any hook file, and thus trigger that hook by passing
|
||||
a to-be-tested file as parameter. The hook will take that file and run it's checks, potentially allowing us to debug
|
||||
and therefore find possible problems.
|
||||
|
||||
testing_class.py is a to-be-tested file example, used to test check_class_docstring hook.
|
||||
|
||||
testing_view.xml is a to-be-tested file example, used to test check_view_name Odoo specific hook.
|
||||
Loading…
Add table
Add a link
Reference in a new issue