Files
autospec/tests
William Douglas 750e50d160 Add support for building APX binaries
Add early support for APX builds in autospec. This change also makes
APX disabled by default for now but may revert back to enabled by
default in the future. The APX prefix will be /VA as the arch flag is
not yet finalized. This also may change in the future though for now
there are no plans to move it.

Currently autotools builds are unable to use this as it detects as a
cross compilation.

Currently only C using GCC is supported.

This change also reworks how R language optimized binaries are built
and distributed. They will now work as all the other tooling does with
the /VX prefix.

Signed-off-by: William Douglas <william.douglas@intel.com>
2024-02-03 07:25:59 -08:00
..
2023-03-23 16:27:56 -07:00
2017-01-24 15:01:38 -08:00
2022-01-21 11:42:56 -08:00
2019-07-11 13:43:02 -07:00
2022-01-12 04:44:34 -08:00

================
Autospec Testing
================

Code Style
==========

Autospec changes are scanned to vet code style issues with the ``flake8`` tool.
To check for issues, run ``make check`` from the root of the autospec source
tree, which executes ``flake8`` with appropriate arguments.

Unit
====

Autospec ships with several test modules that correspond to individual modules
from the toplevel ``autospec`` directory.

Each module can be tested in isolation by running ``make test_<MODULE>``, where
``<MODULE>`` corresponds to the module name. For example, ``make
test_pkg_integrity`` runs unit tests for the ``pkg_integrity.py`` module.

To run *all* unit tests, run ``make unittests``. If all tests pass, a code
coverage report is also generated.