Skip to content

3.8.0: Importer Improvements
Compare
Choose a tag to compare
@kaklakariada kaklakariada released this 26 Feb 13:38
· 17 commits to main since this release
3.8.0
ea8baaf
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Summary

In this release we derived a parser for Restructured Text (RST) from our existing Markdown parser.

The Markdown parser in the process now accepts specification item titles underlined with either "=" (H1) or "-" (H2).

Also, the Markdown parser now ignores whitespace in Needs and Tags entries and correctly parses Tags at the start of a requirement item.

The test coverage for the Markdown importer is now at 100%, and we were able to remove tests that were done with mocks in favor or more robust low-level integration tests.

The HTML report now allows expanding all details sections with command line option --details-section-display expand.

Now you can also specify a revision for coverage tags instead of the default revision 0, e.g. [impl~~42->req~example_name~17].

Features

  • #378: Added an RST importer
  • #377: Allow expanding the details sections in the HTML report
  • #379: Allow specifying a revision for coverage tags
  • #394: Import coverage tags from .yml files in addition to .yaml

Bugfixes

  • #366: Allow all unicode characters in names of specification ID names (thanks to @sebastianohl for the bug report!)
  • #373: Ignore spaces after items in "Needs:" and "Tags:" lists (thanks to @sambishop for his contribution!)
  • #378: Merged integration test coverage with unit test coverage for representative overall figure
  • #303: Escape special characters in HTML report to avoid broken HTML when a specification item contains text like <section>
  • #391: Fixed reading files with invalid encoding (thanks to @ayankuma for the bug report!)

Refactoring

  • #222: Fixed Java compiler warnings
Assets 3
Loading