Task #4380
closed
Run integration tests for every Jenkins build
Added by Eric Newberry about 7 years ago.
Updated about 1 year ago.
Category:
Integration Tests
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).
I couldn't agree more, but I thought we tried to do this in the past and we gave up for some reason..?
- Related to Task #1948: Run integrated tests for every Jenkins build added
- Blocked by Bug #4379: integration tests: fix broken tests added
- Blocked by Feature #1895: Clone from alternate code branch in integration tests added
I think this should be indicated on Gerrit with a "Verified-Integration" label, like is used for NLSR.
- Blocked by Bug #4410: `run_tests.py test_ndnping` fails to terminate added
- Assignee deleted (
Eric Newberry)
- Target version deleted (
v0.7)
- Related to Feature #5108: Support running NFD integration tests in Docker containers added
- Assignee set to Eric Newberry
- Category changed from Build to Integration Tests
- Assignee deleted (
Eric Newberry)
- Status changed from New to Abandoned
Also available in: Atom
PDF