mirror of https://github.com/ansible/ansible.git
Initial ansible-test sanity docs. (#26775)
* Rename no-iterkeys test for consistency. * Require docs for all ansible-test sanity tests. * Initial ansible-test sanity docs. * Fix capitalization of Python. * Fix sanity code smell test false positives. * Fix another code-smell false positive.pull/26810/head
parent
b9a1998af5
commit
789218c215
@ -0,0 +1,12 @@
|
||||
#!/bin/bash -eu
|
||||
|
||||
cat <<- EOF > ../docsite/rst/dev_guide/testing/sanity/index.rst
|
||||
Sanity Tests
|
||||
============
|
||||
|
||||
The following sanity tests are available as \`\`--test\`\` options for \`\`ansible-test sanity\`\`:
|
||||
|
||||
$(for test in $(../../test/runner/ansible-test sanity --list-tests); do echo "- :doc:\`${test} <${test}>\`"; done)
|
||||
|
||||
This list is also available using \`\`ansible-test sanity --list-tests\`\`.
|
||||
EOF
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » ansible-doc
|
||||
==========================
|
||||
|
||||
Verifies that ``ansible-doc`` can parse module documentation on all supported Python versions.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » ansible-var-precedence-check
|
||||
===========================================
|
||||
|
||||
Check the order of precedence for Ansible variables against :doc:`variable_precedence`.
|
@ -0,0 +1,11 @@
|
||||
Sanity Tests » boilerplate
|
||||
==========================
|
||||
|
||||
Most Python files other than those under ``lib/ansible/modules/`` should include the following boilerplate:
|
||||
|
||||
.. code-block:: python
|
||||
|
||||
from __future__ import (absolute_import, division, print_function)
|
||||
|
||||
__metaclass__ = type
|
||||
|
@ -0,0 +1,5 @@
|
||||
Sanity Tests » configure-remoting-ps1
|
||||
=====================================
|
||||
|
||||
The file ``examples/scripts/ConfigureRemotingForAnsible.ps1`` is required and must be a regular file.
|
||||
It is used by external automated processes and cannot be moved, renamed or replaced with a symbolic link.
|
@ -0,0 +1,7 @@
|
||||
Sanity Tests » empty-init
|
||||
=========================
|
||||
|
||||
The ``__init__.py`` files under the following directories must be empty:
|
||||
|
||||
- ``lib/ansible/modules/``
|
||||
- ``test/units/``
|
@ -0,0 +1,5 @@
|
||||
Sanity Tests » import
|
||||
=====================
|
||||
|
||||
All Python imports in ``lib/ansible/modules/`` and ``lib/ansible/module_utils/`` which are not from the Python standard library
|
||||
must be imported in a try/except ImportError block.
|
@ -0,0 +1,36 @@
|
||||
Sanity Tests » integration-aliases
|
||||
==================================
|
||||
|
||||
Each integration test must have an ``aliases`` file to control test execution.
|
||||
|
||||
If the tests cannot be run as part of CI (requires external services, unsupported dependencies, etc.),
|
||||
then they most likely belong in ``test/integration/roles/`` instead of ``test/integration/targets/``.
|
||||
In that case, do not add an ``aliases`` file. Instead, just relocate the tests.
|
||||
|
||||
In some cases tests requiring external resources can be run as a part of CI.
|
||||
This is often true when those resources can be provided by a docker container.
|
||||
|
||||
However, if you think that the tests should be able to be supported by CI, please discuss test
|
||||
organization with @mattclay or @gundalow on GitHub or #ansible-devel on IRC.
|
||||
|
||||
If the tests can be run as part of CI, you'll need to add an appropriate CI alias, such as:
|
||||
|
||||
- ``posix/ci/group1``
|
||||
- ``windows/ci/group2``
|
||||
|
||||
The CI groups are used to balance tests across multiple jobs to minimize test run time.
|
||||
Using the relevant ``group1`` entry is fine in most cases. Groups can be changed later to redistribute tests.
|
||||
|
||||
Aliases can also be used to express test requirements:
|
||||
|
||||
- ``needs/privileged``
|
||||
- ``needs/root``
|
||||
- ``needs/ssh``
|
||||
|
||||
Other aliases are used to skip tests under certain conditions:
|
||||
|
||||
- ``skip/freebsd``
|
||||
- ``skip/osx``
|
||||
- ``skip/python3``
|
||||
|
||||
Take a look at existing ``aliases`` files to see what aliases are available and how they're used.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » line-endings
|
||||
===========================
|
||||
|
||||
All files must use ``\n`` for line endings instead of ``\r\n``.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » no-basestring
|
||||
============================
|
||||
|
||||
Do not use ``isinstance(s, basestring)``.
|
@ -0,0 +1,16 @@
|
||||
Sanity Tests » no-dict-iteritems
|
||||
================================
|
||||
|
||||
The ``dict.iteritems`` method has been removed in Python 3. There are two recommended alternatives:
|
||||
|
||||
.. code-block:: python
|
||||
|
||||
for KEY, VALUE in DICT.items():
|
||||
pass
|
||||
|
||||
.. code-block:: python
|
||||
|
||||
from ansible.module_utils.six import iteritems
|
||||
|
||||
for KEY, VALUE in iteritems(DICT):
|
||||
pass
|
@ -0,0 +1,9 @@
|
||||
Sanity Tests » no-dict-iterkeys
|
||||
===============================
|
||||
|
||||
The ``dict.iterkeys`` method has been removed in Python 3. Use the following instead:
|
||||
|
||||
.. code-block:: python
|
||||
|
||||
for KEY in DICT:
|
||||
pass
|
@ -0,0 +1,16 @@
|
||||
Sanity Tests » no-dict-itervalues
|
||||
=================================
|
||||
|
||||
The ``dict.itervalues`` method has been removed in Python 3. There are two recommended alternatives:
|
||||
|
||||
.. code-block:: python
|
||||
|
||||
for VALUE in DICT.values():
|
||||
pass
|
||||
|
||||
.. code-block:: python
|
||||
|
||||
from ansible.module_utils.six import itervalues
|
||||
|
||||
for VALUE in itervalues(DICT):
|
||||
pass
|
@ -0,0 +1,8 @@
|
||||
Sanity Tests » no-list-cmp
|
||||
==========================
|
||||
|
||||
The ``cmp`` function has been removed in Python 3.
|
||||
|
||||
See `When sorting, use key instead of cmp`_.
|
||||
|
||||
.. _When sorting, use key instead of cmp: http://python3porting.com/preparing.html#when-sorting-use-key-instead-of-cmp
|
@ -0,0 +1,6 @@
|
||||
Sanity Tests » pep8
|
||||
===================
|
||||
|
||||
Python static analysis for PEP 8 style guideline compliance.
|
||||
|
||||
See :doc:`testing_pep8` for more information.
|
@ -0,0 +1,6 @@
|
||||
Sanity Tests » pylint-ansible-test
|
||||
==================================
|
||||
|
||||
Python static analysis for common programming errors.
|
||||
|
||||
A more strict set of rules applied to ``ansible-test``.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » pylint
|
||||
=====================
|
||||
|
||||
Python static analysis for common programming errors.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » replace-urlopen
|
||||
==============================
|
||||
|
||||
Use ``open_url`` from ``module_utils`` instead of ``urlopen``.
|
@ -0,0 +1,5 @@
|
||||
Sanity Tests » required-and-default-attributes
|
||||
==============================================
|
||||
|
||||
Use only one of ``default`` or ``required`` with ``FieldAttribute``.
|
||||
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » rstcheck
|
||||
=======================
|
||||
|
||||
Check reStructuredText files for syntax and formatting issues.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » sanity-docs
|
||||
==========================
|
||||
|
||||
Documentation for each ``ansible-test sanity`` test is required.
|
@ -0,0 +1,16 @@
|
||||
Sanity Tests » shebang
|
||||
======================
|
||||
|
||||
Most executable files should only use one of the following shebangs:
|
||||
|
||||
- ``#!/bin/sh``
|
||||
- ``#!/bin/bash``
|
||||
- ``#!/usr/bin/make``
|
||||
- ``#!/usr/bin/env python``
|
||||
- ``#!/usr/bin/env bash``
|
||||
|
||||
NOTE: For ``#!/bin/bash``, any of the options ``eux`` may also be used, such as ``#!/bin/bash -eux``.
|
||||
|
||||
This does not apply to Ansible modules, which should not be executable and must always use ``#!/usr/bin/python``.
|
||||
|
||||
Some exceptions are permitted. Ask if you have questions.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » shellcheck
|
||||
=========================
|
||||
|
||||
Static code analysis for shell scripts using the excellent `shellcheck <https://www.shellcheck.net/>`_ tool.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » test-constraints
|
||||
===============================
|
||||
|
||||
Constraints for test requirements should be in ``test/runner/requirements/constraints.txt``.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » use-compat-six
|
||||
=============================
|
||||
|
||||
Use ``six`` from ``module_utils`` instead of ``six``.
|
@ -0,0 +1,6 @@
|
||||
Sanity Tests » validate-modules
|
||||
===============================
|
||||
|
||||
Analyze modules for common issues in code and documentation.
|
||||
|
||||
See :doc:`testing_validate-modules` for more information.
|
@ -0,0 +1,4 @@
|
||||
Sanity Tests » yamllint
|
||||
=======================
|
||||
|
||||
Check YAML files for syntax and formatting issues.
|
Loading…
Reference in New Issue