Criterion/doc/faq.rst

24 lines
910 B
ReStructuredText
Raw Permalink Normal View History

2015-03-23 20:11:25 +01:00
F.A.Q
=====
2015-03-23 20:34:52 +01:00
**Q. When running the test suite in Windows' cmd.exe, the test executable
2015-03-23 20:11:25 +01:00
prints weird characters, how do I fix that?**
2015-03-23 20:34:52 +01:00
2015-03-23 20:11:25 +01:00
A. Windows' ``cmd.exe`` is not an unicode ANSI-compatible terminal emulator.
There are plenty of ways to fix that behaviour:
2015-03-23 20:34:52 +01:00
2015-03-23 20:11:25 +01:00
* Pass ``--ascii`` to the test suite when executing.
* Define the ``CRITERION_USE_ASCII`` environment variable to ``1``.
* Get a better terminal emulator, such as the one shipped with Git or Cygwin.
**Q. I'm having an issue with the library, what can I do ?**
2015-03-23 20:34:52 +01:00
2015-03-23 20:11:25 +01:00
A. Open a new issue on the `github issue tracker <https://github.com/Snaipe/Criterion/issues>`_,
and describe the problem you are experiencing, along with the platform you are
running criterion on.
**Q. Why does Gcov show 0% coverage after I run my tests?**
You need to either pass ``--no-early-exit`` or define
``CRITERION_NO_EARLY_EXIT=1`` in your environment to get proper coverage.