Project

General

Profile

Bug #3268

execute TTCN3 test suites against "latest" feeds

Added by laforge 9 days ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
05/15/2018
Due date:
% Done:

0%

Spec Reference:

Description

It would be good to run our test suites not only against current master builds, but also against the "latest" packages. This way we can nicely show the amount of bugs fixed (and/or regressions pending) between the latest tagged version[s] and the current master.

In I6a564206dd81743deb1eb27eca7081bc333d7434 of docker-playground.git I already introduced Dockerfiles:

osmo-bsc-latest
osmo-bts-latest
osmo-ggsn-latest
osmo-hlr-latest
osmo-hnbgw-latest
osmo-mgw-latest
osmo-msc-latest
osmo-sgsn-latest
osmo-sip-latest
osmo-stp-latest
What's missing is mainly
  • generalization of the "jenkins.sh" scripts to either test master or latets
  • migration of ttcn3 jenkins jobs to JJB, so we can template them and duplicate them

Potential problems: The tests use hard-coded IP addresses, and docker cannot have two networks with overlapping addresses, even if there's no routing between them :( We would then have to make sure that no ttcn3-bts-test-master and ttcn3-bts-test-latest jobs are running in parallel on the same build slave. A possible work-around would be to have separate build slaves for master/latest. Using different IP addresses (172.18.9.0/24 for ttcn3-bts-test-master and 172.17.9.0/24 for ttcn3-bts-test-latest) is of course desirable, but this would require different osmo-*.cfg and different TTCN-3 testsuite config files, etc :(((

Also available in: Atom PDF