summaryrefslogtreecommitdiffstats
path: root/testing
Commit message (Collapse)AuthorAgeFilesLines
* Incorrect number tag sequence for xhtml with htmlinclude command possiblealbert-github2018-11-252-2/+2
| | | | | | Analogous to the `\htmlonly` also with the `\htmlinclude` command it is possible that some parts are added that cannot be inside a `<p> ... <\/p>` and thus we have to temporary close (and later reopen) the paragraph. The option `[block]` has been added to the `\htmlinclude` command (analogous to the `\htmlonly` command). Problem can be seen with the default doxygen test 30 (`[030_htmlinclude.dox]: test the \htmlinclude command`).
* Multiple `\xreflist` in one page with same keyalbert-github2018-10-315-21/+20
| | | | Regression regarding tests
* Merge pull request #6438 from albert-github/feature/bug_citeDimitri van Heesch2018-10-281-1/+1
|\ | | | | Correcting labels for citations
| * Correcting labels for citationsalbert-github2018-08-101-1/+1
| | | | | | | | Corrected change in test.
* | Merge pull request #6486 from albert-github/feature/bug_tests_extensionsDimitri van Heesch2018-10-272-16/+111
|\ \ | | | | | | Extending tests with extra possibilities
| * \ Merge branch 'master' into feature/bug_tests_extensionsDimitri van Heesch2018-09-152-0/+11
| |\ \
| * | | Extending tests with extra possibilitiesalbert-github2018-09-072-15/+111
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - docbook for docbook output including small test on validity (i.e. basic xml test) - rtf for rtf output - start_id and end_id creating the possibility to run one range of tests -- subdirs us CREATE_SUBDIRS=YES
* | | | Merge pull request #6487 from albert-github/feature/bug_docbookDimitri van Heesch2018-09-153-1/+3
|\ \ \ \ | |_|/ / |/| | | Implementation of standard generator for docbook output
| * | | Implementation of standard generator for docbook outputalbert-github2018-09-073-1/+3
| |/ / | | | | | | | | | | | | | | | | | | | | | Till now docbook had its own output generator, but lot of possibilities were missing (see remark about updating below), with this patch the (more than) basic implementation has been made. Added some docbook tests to the current tests and updated documentation where necessary Tried updating current version but too many issues remained that were generically handled in the standard generator, code is in current version behind '#if 0' construct in doxygen.cpp and name with '_v1' and in docbookgen.cp'
* | | Add possibility for adding doxygen configuration items to, all, tests during ↵albert-github2018-09-152-1/+13
|/ / | | | | | | | | | | runtime. Creating possibility to add extra doxygen configuration items to tests (e.g. QUIET=NO)
* | Merge pull request #6468 from arm-in/masterDimitri van Heesch2018-09-031-3/+2
|\ \ | | | | | | Typos found by running "codespell"
| * | Update README.txtArmin Müller2018-08-301-3/+2
| |/
* | Merge pull request #6481 from albert-github/feature/bug_test_005_typoDimitri van Heesch2018-09-031-1/+1
|\ \ | | | | | | Correct typing error in test 5
| * | Correct typing error in test 5albert-github2018-09-031-1/+1
| |/
* | Correct typing error in test 51albert-github2018-09-032-2/+2
|/
* Enable in page table of contents for XML and add maximum level to in page ↵albert-github2018-07-122-2/+29
| | | | | | | table of contents - correction of compiler error (not caught on Windows) - updated test 43 (for in page toc)
* Merge pull request #714 from albert-github/feature/bug_test_condDimitri van Heesch2018-06-102-2/+6
|\ | | | | Problem with \cond in normal comment of test 015
| * Problem with \cond in normal comment of test 015albert-github2018-05-072-2/+6
| | | | | | | | | | | | | | | | In the \cond is also recognized in non-doxygen comment. - As a work around the \ has been removed - in case of e.g. pdf the enabled function is not shown as it does not have a doxygen comment - test file output update due to change in input code. - pre.l and commentcnv.l. better error message i.e. showing better the used condition
* | Problem with TEST_FLAGS when using CMake for Visual StudioTushar Maheshwari2018-05-132-3/+4
|/
* Merge pull request #693 from albert-github/feature/bug_tests_xhtml_pdfDimitri van Heesch2018-04-227-49/+2874
|\ | | | | Create test possibilities for xhtml and pdf output
| * Create test possibilities for xhtml and pdf outputalbert-github2018-04-031-3/+3
| | | | | | | | Regression of default output (INPUT setting was overruled).
| * Create test possibilities for xhtml and pdf outputalbert-github2018-04-037-52/+2877
| | | | | | | | | | | | The tests in the testing directory provided possibilities to do some regression tests based on the xml output. With the option --xhtml it is possible to see whether or not a test or set of tests is xhtml compliant. With the option --pdf it is possible to see whether or not a test or set of tests can be build to a pdf file (per test).
* | Merge pull request #690 from albert-github/feature/bug_test_numbersDimitri van Heesch2018-04-224-12/+12
|\ \ | | | | | | Test renumbering
| * | Test renumberingalbert-github2018-04-014-71/+0
| | | | | | | | | | | | The tests numbers 067 and 068 were used twice, test 067 has been renamed to 072 and test 068 has been renamed to 073.
| * | Test renumberingalbert-github2018-04-014-0/+71
| |/ | | | | | | The tests numbers 067 and 068 were used twice, test 067 has been renamed to 072 and test 068 has been renamed to 073.
* | Merge pull request #685 from albert-github/feature/bug_single_testsDimitri van Heesch2018-04-221-2/+2
|\ \ | | | | | | Enable possibility to run single tests
| * | Enable possibility to run single testsalbert-github2018-03-271-2/+2
| |/ | | | | | | Create the possibility to run only one or more tests.
* | Merge pull request #682 from arm-in/masterDimitri van Heesch2018-04-221-1/+1
|\ \ | | | | | | Typos found by running "codespell"
| * | TypoArmin Müller2018-03-261-1/+1
| |/
* | Bug 792122 - XHTML pages are broken several waysalbert-github2018-03-042-3/+121
|/ | | | | | | | | | | | | | | | | | | The Markdown processing was done after the normal tag processing and splitting the comment in brief, doc, inline. This resulted in that sectioning parts (i.e. e.g. ==== conversion to <h1> ) remained in the brief description whilst similar constructs with HTML commands landed in the doc (details) description. By performing the markdown on the entire comment block this problem has been overcome. commentscan.l - change moment of calling markdown processing - skip start spaces and subsequent empty lines in markdown processed code - small debug correction markdown.cpp - don't convert the dashes in <!-- and --> (HTML type comment) - small debug correction 054 test - update of example for compatibility and adding part about none code result. doxygen.cpp - small textual comment correction
* XML output: avoid warnings with scoped enum values in anonymous namespaces.Vladimír Vondruš2017-12-292-0/+57
| | | | | | | | | | | | | | | | | | | | | | When a C++11 `enum class` was present in an anonymous namespace (usually in *.cpp files), the XML output was emitting warnings similar to the following: Internal inconsistency: member False does not belong to any container! And the XML output was rendering bogus IDs for enum values starting with `dummy_`, such as: dummy_1a96ab6574751fdf6a53ceec8a3896c45daf8320b26d30ab433c5a54546d21f414c The fix is to call memberOutputFileBase() on the enumeration itself and not on the enum value, that way it provides correct file base that corresponds to file base of the enumeration. There's also a new test that checks this. Note: this assumes that enum values belong to the same compound as enums themselves. In my experience that was always the case and there's no broken test after this change, so I hope I didn't break anything.
* Merge branch 'variadic' of https://github.com/mehw/doxygen into mehw-variadicDimitri van Heesch2017-12-278-0/+956
|\
| * Add variadic template function regression testsMatthew White2017-08-034-0/+808
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * testing/069_link_variadic_template.cpp: new file, @link regression test for variadic template function * testing/069/069__link__variadic__template_8cpp.xml: new file, expected @link regression test result for variadic template function * testing/070_ref_variadic_template.cpp: new file, @ref regression test for variadic template function * testing/070/070__ref__variadic__template_8cpp.xml: new file, expected @ref regression test result for variadic template function At the time of writing, the part between <> is totally ignored: func<Args...>(Args... args) is interpreted as func(Args... args). Beware that a function parameter with either a & or * operator, e.g. 'const Args&... args', requires @link and @ref to use such parameter as verbatim, i.e. {@link func(const Args&... args)}. At the time of writing, the form {@link func(const Args&...)} will fail, unless the function parameter was declared just as 'const Args&...'.
| * Add variadic function arguments '...' regression testsMatthew White2017-08-034-0/+148
| | | | | | | | | | | | | | | | | | | | | | * testing/067_link_varargs.cpp: new file, @link regression test for variadic function arguments '...' * testing/067/067__link__varargs_8cpp.xml: new file, expected @link regression test result for variadic function arguments '...' * testing/068_ref_varargs.cpp: new file, @ref regression test for variadic function arguments '...' * testing/068/068__ref__varargs_8cpp.xml: new file, expected @ref regression test result for variadic function arguments '...'
* | Merge pull request #627 from mosra/xml-strong-typed-enumsDimitri van Heesch2017-12-243-1/+34
|\ \ | | | | | | Full support for strong and typed enums in the XML output
| * | Provide information about enum type "strongness" in the XML output.Vladimír Vondruš2017-11-292-2/+2
| | | | | | | | | | | | | | | | | | | | | There's a new boolean `strong` attribute on the `<memberdef>` element that defines whether the enum is a classic or a strong one. Tests were updated to verify both cases.
| * | Expose underlying enum type in the XML output.Vladimír Vondruš2017-11-293-0/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The <type> element (used for function return type and variable type) is now reused also for underlying enum type. C++03-style enum types that don't have the underlying type specified have the <type> tag as well, but empty to indicate that the underlying type is unspecified. Added a new test case for this.
* | | Merge pull request #626 from mosra/xml-using-templatesDimitri van Heesch2017-12-242-0/+39
|\ \ \ | | | | | | | | Provide template parameters also for type aliases in the XML output
| * | | Provide template parameters also for type aliases in the XML output.Vladimír Vondruš2017-11-282-0/+39
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Until now, probably due to C++03 assumptions, typedefs and type aliases skipped printing of the template parameter specifications to the XML output. That's now fixed, so the following type alias will properly contain <templateparamlist> in the XML output: template<class T> using Vec = std::vector<T>; Added also a test case that verifies this.
* | | Merge pull request #625 from mosra/xml-tableofcontentsDimitri van Heesch2017-12-242-0/+3
|\ \ \ | | | | | | | | Expose TOC placeholder in XML output
| * | | Expose TOC placeholder in XML output.Vladimír Vondruš2017-11-292-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently the XML output for a page was generated the same independently of whether the \tableofcontents command was present in the page source or not. Because of that, the users of the XML output had no chance of knowing whether given page should have a TOC or not. There's now a new <tableofcontents> element that gets added in case the TOC was requested. As it is trivial to populate the TOC on user side by simply enumerating the <sectN> elements, the element is empty and acts just as a boolean.
* | | | Merge pull request #624 from mosra/xml-page-briefdescriptionDimitri van Heesch2017-12-2442-0/+86
|\ \ \ \ | |/ / / | | | | Provide page brief in <briefdescription> of XML output
| * | | Provide page brief in <briefdescription> of XML output.Vladimír Vondruš2017-11-2542-0/+86
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Until now the brief description of pages was prepended to the <detaileddescription> element and the <briefdescription> element was not present at all, which meant there was no easy way to extract the brief description for purposes of creating a page index, for example. With this patch, the brief description is included in both <briefdescription> and <detaileddescription>, thus duplicated, to avoid backwards compatibility issues.
* | | Encode invalid XML characters instead of skipping them.Vladimír Vondruš2017-11-253-2/+4
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The <sp> element in <programlisting> has a new optional attribute `value`, which contains value of given invalid ASCII character. In case of space, the `value` attribute is omitted. Use cases for this: including snippets of *very esoteric* languages, markup that makes use of the advanced ASCII formatting characters or for example highlighting a console output containing ANSI color codes (which is my case, in fact). Regarding backwards compatibility -- as files with such ASCII characters are very rare, I don't expect this minor difference in the output to be a problem. Besides that, such ASCII characters are often replaced by a space in many applications anyway. A test snippet was extended to contain a special character so this difference in behavior could be verified.
* | Propagate language information to all <programlisting> XML elements.Vladimír Vondruš2017-11-196-6/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is based on work done in 141dbfd5a4f79c98da14a1b414c6db4e1b34618b through ed9acb6e1bb81a2eec334180f7b8c1bf0598b444 and makes a few behavioral changes to it. There's a new attribute called `filename` and the `language` was removed, because it could provide misleading information. This allows for more flexibility on the user side. In particular: * For historical reasons, `*.txt` files are marked by Doxygen as C++ (see https://bugzilla.gnome.org/show_bug.cgi?id=760836 for details). In particular, code snippet included from a CMakeLists.txt file would be marked and highlighted as C++. So in this case, the language attribute would be very misleading. * Doxygen is aware only of a very small subset of languages and thus a lot of information can be lost when relying on its extension-to-language-name conversion -- in particular, all extensions that are not recognized are assumed to be C++. On the other hand, putting more effort into its language detection algorithms is not worth the time, as there will always be new languages that fail to detect. So let's leave that on the user of the XML output instead. * Using just file extension is not enough, it has to be a full filename. For example, `*.txt` can be either a plain text file or a `CMakeLists.txt`. * The path is not stripped from the filename, as it also may contain additional information that helps to detect the language better. In addition to that, filenames of code snippets included via the \include command and related are propagated to the <programlisting> element as well. With this change, (1) code snippets using simply \code some code \endcode will not produce any `filename` attribute and it's up to the user what to do -- assume C++, detect language from contents or not highlight anything. <programlisting> some code </programlisting> (2) Code snippets using \code{.cmake} some code \endcode will produce the following: <programlisting filename=".cmake"> some code </programlisting> (3) And finally, \include, \dontinclude and related \skip, \skipline etc. commands \include path/to/some-file.py will produce <programlisting filename="path/to/some-file.py"> some code </programlisting> The tests were updated to check all three cases. On the user side, when using Pygments for example, it's then just a matter of calling pygments.lexers.find_lexer_class_for_filename() with value of the `filename` attribute value and optionally also the code snippet for additional language analysis.
* | Restore 'make tests' ruleDimitri van Heesch2017-10-281-0/+5
| |
* | CMake: use add_test to create a testRolf Eike Beer2017-10-201-4/+2
| | | | | | | | | | This checks the calling from "make tests" to "make test", but lets CMake handle all the rest.
* | CMake: remove unused program searchingRolf Eike Beer2017-10-201-3/+0
| |
* | Use language identifier instead of file extension for language attributeDimitri van Heesch2017-09-281-2/+2
| |
* | fix test to support new programlisting attributeShi Yan2017-09-261-2/+2
|/ | | | | fix unit test to support the new programlisting attribute "language"
generated by cgit v0.12 at 2024-11-01 03:39:30 (GMT)