mirror of
https://github.com/GNS3/gns3-server.git
synced 2026-10-13 05:55:35 +03:00
5c2c8cdb0c
Live e2e verification moves into the repository instead of being rewritten as a throwaway script every time: tests/e2e/ carries a shared harness (REST client, isolated-instance lifecycle, a deliberately dumb IOS console driver, host-side kernel inspection: bridge membership, tap admin state, tc qdiscs) and each node type adds only its scenario module. The e2e marker plus 'addopts = -m "not e2e"' keeps these privileged, image-dependent tests out of normal runs; they are opt-in: pytest -m e2e tests/e2e -s. The harness targets an existing server via GNS3_E2E_URL or starts an isolated instance (own config dir — DB and paths follow it — on a free port) and deletes its project afterwards (GNS3_E2E_KEEP=1 keeps it on failure). The first scenario drives two real c7200 routers on a real IOS image through the REST API and the consoles: the kernel link is created while the routers are stopped (deferred wiring), the per-link kernel bridge enslaves exactly the two anchors, real ICMP crosses it, delay 100 shows netem on both anchors and grows the RTT (~200 ms), suspend kills the traffic on an admin-down anchor, capture writes a pcap of ICMP records, a serial link between the same routers stays on the relay and still pings, delete/ re-create and stop/start leave the wiring consistent, and deleting the project removes every anchor and bridge. A negative control runs the same topology on an isolated relay-configured instance (no per-link bridge, nothing enslaved, still pings).
47 lines
2.0 KiB
Markdown
47 lines
2.0 KiB
Markdown
<!--
|
|
SPDX-License-Identifier: CC-BY-SA-4.0
|
|
See LICENSE file for licensing information.
|
|
-->
|
|
|
|
# Live end-to-end tests
|
|
|
|
Tests under this directory run against a **real** server: real uBridge, real
|
|
kernel interfaces (privileged), real emulator binaries and real images. They
|
|
verify what unit tests cannot — that a datapath actually forwards traffic,
|
|
that kernel bridges actually enslave anchors, that tc impairments actually
|
|
shape packets. They are marked `e2e` and **excluded from normal test runs**
|
|
(see `tests/pytest.ini`); run them explicitly:
|
|
|
|
```bash
|
|
pytest -m e2e tests/e2e -s # -s shows the progress prints
|
|
pytest -m e2e tests/e2e -k dynamips # one scenario
|
|
```
|
|
|
|
Two run modes, chosen per test through `harness.live_server(kernel=...)`:
|
|
|
|
* **Target an existing server** — set `GNS3_E2E_URL` (e.g.
|
|
`http://127.0.0.1:3080/v3`, plus `GNS3_E2E_USER`/`GNS3_E2E_PASSWORD`,
|
|
default admin/admin). The server must already be configured for the
|
|
datapath under test (kernel links need `enable_kernel_datapath = True`).
|
|
* **Isolated instance** (the default) — the harness starts its own server
|
|
process on a free port with its own config directory (the controller DB
|
|
and every path follow the config), so nothing on the machine is touched.
|
|
It needs `ubridge`, `dynamips` and an images directory
|
|
(`GNS3_E2E_IMAGES`, default `~/GNS3/images`) available locally.
|
|
|
|
Either way each test creates its own project and deletes it again. Set
|
|
`GNS3_E2E_KEEP=1` to keep the project (and a started instance) on failure
|
|
and print where to look at it.
|
|
|
|
`harness.py` holds the shared pieces — REST client, server lifecycle, the
|
|
IOS console driver, host-side kernel inspections (bridge membership, tap
|
|
admin state, tc qdiscs) — so a new node type adds only its own scenario
|
|
module.
|
|
|
|
Current scenarios:
|
|
|
|
* `test_dynamips_kernel_datapath.py` — two real c7200 routers: kernel link
|
|
(anchors, per-link bridge, netem delay, suspend, capture, delete/re-create,
|
|
stop/start) plus a serial link staying on the relay, and a negative
|
|
control on an isolated relay-configured instance.
|