Visitar URL original
Update unit testing strategy · Issue #253 · trigger/trigger · GitHub
Skip to content

Update unit testing strategy #253

Open

Description

@tcuthbert

Outline

An update of the unit testing strategy is required to help catch low-level issues before being committed.

For example #252 is an issue that could have been caught in the integration phase.

Proposed Changes

  1. Utilise MockSSH to simulate return SSH data. This will help mitigate issues that arise from untested data processing functions such as the TextFSM parser.
    2.A Functional testing workflow definition will improve our ability to catch issues that surface in production. A combination of Docker and something like TestInfra to assert network state might be a good idea.

Activity

  1. self-assigned this
    on Mar 3, 2016
  2. jathanism commented on Mar 3, 2016

    @jathanism
    Member

    Related or dupe of #161

  3. jathanism commented on Feb 6, 2026

    @jathanism
    Member

    v2.0.0 Update: The pytest migration is now complete — Trigger v2.0.0 uses pytest as its test runner with all tests passing under Python 3.10-3.11.

    The remaining value in this issue is around:

    1. MockSSH-based testing — simulating SSH return data for testing data processing functions (TextFSM parser, command execution)
    2. Functional/integration testing — Docker-based workflow for end-to-end testing against simulated network devices

    Refocusing this issue on these two outstanding proposals.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions