Skip to content

systemd-resolved test suite #19599

@mrc0mmand

Description

@mrc0mmand

This was discussed multiple times both in upstream and in RHEL (from what I know, at least), and given the recent issues reported from Fedora and other distros, it's a pretty actual topic.

So far this is just mostly spitballing to get at least a general idea how the test suite should look like.

A couple of points which come to mind:

  • DNS servers - I suspect we want the test suite to be self-contained (i.e. don't depend on external DNS servers), which means configuring a DNS server (dnsmasq, bind, unbound, etc.). This introduces a whole new set of issues - making the configuration compatible across multiple distributions with multiple versions (maybe wrapping it in a container?), isolation problems (e.g. we want resolved to talk only with the local DNS server), etc.

  • Test suite format - which "style" do we want to use? Bash, to follow the integration test suite, python unittest used by the systemd-networkd test suite, or something completely different?

Please feel free to add more points, ideas, comments, etc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    RFE 🎁Request for Enhancement, i.e. a feature requestresolvetests

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions