nornir-automation / nornir

92%

LAST BUILD ON BRANCH develop

branch: develop

CHANGE BRANCH

x

Reset

• develop
• 1.1.0
• 2.0
• 2.0.0-beta
• allow_filter_i
• attributes_refactor
• bug_in_var_resolution
• bump
• bump_beta_version
• changelog
• cleanup
• config_continue
• contributors
• coverage
• cust_inv_initnornir
• dbarroso/remove_resolver
• debug_vars
• dependabot/pip/h11-0.16.0
• dependabot/pip/jinja2-3.1.5
• dependabot/pip/jupyterlab-4.4.8
• dependabot/pip/requests-2.32.4
• dependabot/pip/setuptools-70.0.0
• dependabot/pip/setuptools-78.1.1
• dependabot/pip/tornado-6.5.1
• dependabot/pip/urllib3-2.5.0
• dependabot/pip/zipp-3.19.1
• django_like_queries
• doc_fix
• doc_fixes
• docs
• docs_final
• docs_transform_function
• feature/add_plugin_list
• filter_netbox
• filter_object
• fix-270
• fix_docs
• fix_license_classifier
• fix_netmiko_enable
• fixes
• howtos
• improve_yaml_loader
• inv_plugins_data
• inventory_rework
• jinja_filters
• locking_mechanism
• main
• master
• multiprocessor-runner-fix
• mypy
• napalm_kwargs
• napalm_yang
• net
• no_config
• nsot_tests
• ogenstad/coverage
• ogenstad/coverage-branch
• ogenstad/python312-tests
• ogenstad/simplify-filter
• ogenstad/test-processors
• ogenstad/test-types
• ogenstad/testing-typing
• ogenstad_connection
• output_test
• parent_groups
• py313_support
• pydantic
• pydantic_update
• pylama
• rebase-2.0
• refactor_connection_plugins
• release
• release_3_5_0
• rename
• rename_abbreviations
• ruaml
• serialize
• ssh_port
• sub_task_exceptions
• tasks_rework
• thread-safety
• update_black
• v0.0.7
• v1.0.0
• v1.0.1
• v1.1.0
• v2.0.0
• v2.0.0b1
• v2.0.0b2
• v3.5.0
• versioning

Build # 1102

Build Type

push

travis-ci

Committed by dbarrosop

Commit Message

Remove the external ping test (#293)

* Remove the external ping test

By having a test for external connectivity which isn't stubbed,
what's actually being tested is the network environment of the development
machine, and not the nornir code. There are several examples where
this test would legitimately fail:
- Offline laptop
- Corporate environment with restrictive firewall policies.

As such, a failing test does not necessarily indicate an issue with the
code. A failed test will cause downstream tools that depend on passing
tests to fail, or leave developers wasting time looking for non-existent
faults.

* Remove resources used by external ping test

Run Details

1408 of 1529 relevant lines covered (92.09%)

0.92 hits per line