Project

General

Profile

Actions

Task #4380

closed

Run integration tests for every Jenkins build

Added by Eric Newberry about 7 years ago. Updated about 1 year ago.

Status:
Abandoned
Priority:
Normal
Assignee:
-
Category:
Integration Tests
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

When Jenkins is testing a change to NFD, ndn-cxx, ndn-tools, or ndn-traffic-generator, it should run the NFD integration test suite against the change and report its success or failure. This would help to ensure that the integration tests stay up to date (and also help us detect changes breaking the compatibility between programs).

This could be set up as a separate Jenkins platform using special VMs running Vagrant and VirtualBox (and with enough RAM and CPU cores to run the 5 integration test VMs concurrently inside the VM).

Likely, this would need to be configured in the ".jenkins.d" directory in each codebase. Separate instructions for the integration testing platform could be used to run the integration tests on the change (and not the standard build and test).


Related issues 5 (1 open4 closed)

Related to ndn-cxx - Task #1948: Run integrated tests for every Jenkins buildNew

Actions
Related to NFD - Feature #5108: Support running NFD integration tests in Docker containersClosedEric Newberry

Actions
Blocked by NFD - Bug #4379: integration tests: fix broken testsAbandoned

Actions
Blocked by NFD - Feature #1895: Clone from alternate code branch in integration testsClosedEric Newberry

Actions
Blocked by NFD - Bug #4410: `run_tests.py test_ndnping` fails to terminateClosedEric Newberry

Actions
Actions

Also available in: Atom PDF