aboutsummaryrefslogtreecommitdiffstats
path: root/ttcn3-bts-test
AgeCommit message (Collapse)AuthorFilesLines
2019-07-10ttcn3-*: enable GSMTAP loggingOliver Smith4-0/+12
Configure each osmo-* program to send GSMTAP log output to the IP of the docker container, which runs the testsuite (and therefore runs tcpdump). Related: https://lists.osmocom.org/pipermail/openbsc/2019-June/012946.html Change-Id: I99e74f6ffb5b7d566cec35995bf067df414968d8
2019-06-04ttcn3-bts-tests: Add BTS_Tests_LAPDm.control to config fileHarald Welte1-0/+1
There's a number of new tests that aren't executed yet. Change-Id: I3bfb4483f39d4dbf3f506f86470e4f2d3b6b7af2
2019-06-03ttcn3-*: Enable extended-timestamp in VTY cfgPau Espin Pedrol1-0/+1
Having extended-timestamp allows for easier matching between osmo-*.log files and pcap traces. Change-Id: I98cdc0adc24edc966d5648d2c215c6ad7c749209
2019-05-29ttcn3-bts-test: Execute OML tests without BSCHarald Welte3-3/+126
Run the testsuite one more time; this time for OML tests which require us to run without a BSC. We can run those with trxcon and omso-bts-trx and don't need virtphy for them. Related: OS#4031 Depends: osmo-ttcn3-hacks I82bb85b684d2db3a6b1e96a68ffde03e22affa6b Change-Id: I97db9c74c56ca93c75e5e5226955799cd945eec0
2019-05-29ttcn3-bts-test: Add virtphy based PCUIF testsHarald Welte3-3/+142
Some tests require GPRS features not yet present in trxcon, so we have to fall back using virtphy. Change-Id: I2f17f03194a4dfa0abca51b0d3e22b3934d08a9a
2019-05-29ttcn3-bts-test/jenkins.sh: Move start of containers into shell functionsHarald Welte1-46/+61
Change-Id: If9ac580aa5f0745468f69d413aa732891acb4a1c
2019-05-23ttcn3-bts-test: Fix BSC VTY access from test suiteHarald Welte2-0/+2
Some tests, particularly those for SMSCB, want to access the BSC VTY. This was enabled in the ttcn3 code, but the configs we're using in the docker environment didn't properly refelect that yet. Change-Id: I6b6e8b47bfe85c15fb57a25b649029f872477146
2019-05-22Fix git checkout for branches and commitsOliver Smith1-1/+2
Replace 'git checkout -f -B $BRANCH origin/$BRANCH && \' in all Dockerfiles that accept branch variables ($OSMO_TTCN3_BRANCH, $OSMO_MGW_BRANCH, ...) with the following: git checkout $BRANCH && \ (git symbolic-ref -q HEAD && git reset --hard origin/$BRANCH || exit 1); \ This allows using branch names and commit hashes in the $BRANCH variables. Using commits is needed for the bisect script added in [1]. The second line ("(git symbolic...") checks if we are in detached HEAD state after the checkout, and if we are not, pulls in all new commits from origin/$BRANCH. Note that it ends in ';' instead of '&&', because the command in the next line should be executed even if "git symbolic-ref" does not exit with 0 (detached HEAD state). Here is an example, to illustrate that the new command does the right thing. Clone a repository and be 50 commits behind origin/master: $ git clone "https://git.osmocom.org/osmo-mgw" $ cd osmo-mgw $ git reset --hard origin/master~50 With BRANCH="master": $ git checkout master && \ (git symbolic-ref -q HEAD && git reset --hard origin/master || exit 1); \ echo "done" Already on 'master' ... done $ git status Your branch is up-to-date with 'origin/master'. With BRANCH="85978d": $ git checkout 85978d && \ (git symbolic-ref -q HEAD && git reset --hard origin/85978d || exit 1); \ echo "done" Note: checking out '85978d'. ... done $ git status HEAD detached at 85978dad Related previous changes: * [2] made it work for commit hashes, but broke using branch names other than master, and pulling in new commits from master * [3] made branches other than master work again, but did not fix pulling in new commits from master * [4] reverted [3] and the git checkout related part from [2] [1] Change-Id: I11f7e61a9b30d58a0fdfcaf77dde447806bf661f [2] Change-Id: If3bc5fae07cf63c4fef68306be4c4328660bc869 [3] Change-Id: I2ff745c8d19b777d876170d5717c082ceb68a1f3 [4] Change-Id: Ie6da0f9ea96f11407e38545a6b3cf22ef9cadc25 Related: OS#4015 Change-Id: I4004980baf0b7d6096702b6f3067ccbdb369a28c
2019-05-21osmo-bts-test: Enable BTS_Tests_SMSCB.control for CBCH testingHarald Welte1-0/+1
Support for this was introdcued in osmo-ttcn3-hacks Change-Id If4b5a906a0841c0a8c3d7c4e9e5a3d1208ecf16a, but as we have a separate .cfg file here, we must update it, too. Change-Id: Iab0e9a46a8ee429619e9ef9159a631dc44ab5aeb
2019-05-21Revert "Simplify git checkout, allow branches and commits"Harald Welte1-2/+2
Unfortuately this commit will check out *local* master (i.e. the previous checkout) rather than the origin/master as it's supposed to be. This means that ever since merging this patch, our ttcn3 tests were running some "undefined" stale versions and not current master. This reverts commit 26565bb729549152ce8fa89f59df02f37c907c27. Change-Id: Ie6da0f9ea96f11407e38545a6b3cf22ef9cadc25
2019-05-07Simplify git checkout, allow branches and commitsOliver Smith1-2/+2
Replace the following statements: a) "git checkout -f -B $BRANCH origin/$BRANCH" b) "git checkout -f -B $BRANCH $BRANCH" with: c) "git checkout -f $BRANCH" Regarding a), we don't need to specify 'origin/' for each branch, since we are cloning the repositories in the same Dockerfile, and therefore we know for sure that there is only one remote and branch names won't be ambiguous. Removing the 'origin/' allows to put commit hashes into the branch variables (like done in the new bisect script [1]). Version b) does not work with branch names: $ git checkout -f -B osmith/check-imei-before-lu osmith/check-imei-before-lu fatal: Cannot update paths and switch to branch 'osmith/check-imei-before-lu' at the same time. Did you intend to checkout 'osmith/check-imei-before-lu' which can not be resolved as commit? New version c) works with both commits and branches, and it is shorter. [1] Change-Id: I11f7e61a9b30d58a0fdfcaf77dde447806bf661f Change-Id: I2ff745c8d19b777d876170d5717c082ceb68a1f3
2019-03-30Switch all osmo-*-master and ttcn3-*-test from jessie to stretchHarald Welte1-1/+1
Jessie will be EOL in June 2019, let's make the switch to stretch before that. Change-Id: I37a534d07081f3d321869c86d49d03171c8da0c6
2019-03-29print branch name and git commit hash during docker container buildHarald Welte1-0/+1
This is quite useful when looking at jenkins logs to know which exact version was built at the time. Change-Id: Id52c382b454e2beecf46820752aeff15b2c1a0ae
2019-03-21BTS tests: update NSVC config in osmo-bsc.cfgMax1-5/+1
* remove extra NSVC config * use 0.0.0.0 for nsvc 0 The additional nsvc and this particular address are not used for BTS' PCU-related tests in any way and only add confusion. It's likely a result of copy-paste from another test. Change-Id: Ie424107672496df70fc83c8fd6cef99a312fcee7
2019-01-28ttcn3-*-test: don't hardcode /usr/local/bin/Oliver Smith1-3/+3
Remove hardcoded /usr/local/bin/ paths from jenkins.sh. This caused the *-latest tests to fail, as they have the Osmocom binaries in /usr/bin instead of /usr/local/bin. Related: OS#3767 Change-Id: I9d1427e66028ffd15fed211b2dab5adc37718666
2019-01-25ttcn3-bts-test-latest: use osmocom-bb-host-masterOliver Smith1-2/+2
Do not try to run a osmocom-bb-host-latest docker image, which does not exist as we are not tagging release versions for osmocom-bb (yet). This was done right in the docker_images_require call at the top already (which is why it did not try to build such a "-latest" image), but then the script tried to use the "-latest" images anyway (instead of hardcoding "-master"). Related: OS#3767 Change-Id: Ib743f09c71d93bf4c4ad947ef62b37de6b2d7ecc
2019-01-14.../osmo-bsc.cfg: drop deprecated dyn_ts_allow_tch_fVadim Yanitskiy1-1/+0
Since Ib2335d02ea545aff837aadd49f15b2fdb418c46e, this VTY option is deprecated in osmo-bsc, so let's actualize the config files. Change-Id: I709e1afd2a9cccdc92eec312dff607947a10c299
2019-01-14ttcn3-bts-test/jenkins.sh: use logging options of fake_trx.pyVadim Yanitskiy1-1/+5
Change-Id: I32bf66b1320b752450a8cb064348b3c86b1c03cd
2019-01-12BTS_Tests.cfg: use the new 'mp_bts_trxc_ip' parameterVadim Yanitskiy1-1/+1
In I7736abd85407c186856be9f1a22613a1fa6e0c32 'mp_bb_trxc_ip' was renamed to 'mp_bts_trxc_ip'. Let's correct the config. Depends-On: (TTCN) I7736abd85407c186856be9f1a22613a1fa6e0c32 Change-Id: I886b652ddfb1afbfcf15f99672cca1d63fd714fe
2018-12-06bts-test: osmo-bts.cfg: Enable extended timestampPau Espin Pedrol1-0/+1
This way messages appearing in log files can be easily matched against pcap captures. Change-Id: Ic59c0d7ee0d3ce71e807364d156f6e38bc0c74d1
2018-11-01ttcn3-bts-test: Log RACH requests in GSMTAPPau Espin Pedrol1-0/+1
Change-Id: Idae872492a6cf3306fb2e636c54038caa600646b
2018-10-26jenkins.sh: IMAGE_SUFFIX, docker_images_require()Oliver Smith1-4/+13
Default value "master" of the IMAGE_SUFFIX environment variable can be changed to "latest" to test the latest stable builds instead of the nightly ones. Use docker_images_require() to make sure that the required images are existing and up-to-date before running the tests. Related: OS#3268 Change-Id: Idbb708ab16cb71bab5069127945b63388222369e
2018-10-25ttcn3-bts-test: Log fake_trx output to filePau Espin Pedrol1-1/+4
Change-Id: I82a80b045e6f298e5254f42f51dbf8c84013f45c
2018-09-26ensure well-formed config filesHarald Welte2-76/+76
Change-Id: Id687e63c418e2e955ccbb92f2420a80fc0704ea4
2018-09-06Fix "'laforge/debian-jessie-build' not found"Oliver Smith1-1/+2
Instead of hardcoding laforge's username in all FROM statements in the Dockerfiles, make use of the USER variable (as passed through by the "make/Makefile" with "docker build --build-arg USER=..."). Thanks to fixeria for proposing this fix! This requires running docker-ce, old versions of docker (such as the one in the official repositories of the latest Fedora) don't support variables in the FROM line. But docker-ce can be installed after adding docker's 3rd party repositories. Closes: OS#3457 Change-Id: Ic5f11c8a4e247f632cb6aea6d147e94c53e0130f
2018-08-08Rename 'osmocom-bb-trxcon' to 'osmocom-bb-host-master'Vadim Yanitskiy1-2/+2
At the moment, this Docker image does contain not only trxcon, but also FakeTRX, virt_phy, and other host applications, so let's name it properly... Change-Id: Ieba2411230efdedc13afcd62b8b3a2153fbaf0cb
2018-07-06ttcn3-*: Merge logfiles no matter resolution of testsPau Espin Pedrol1-2/+4
Previous to this commit, log messages were not being merged if tests were resolved as failed (test-suite.sh ending with exit code != 0), which can happen if at least one test failed. Change-Id: If293fc2d3182ef2a7b997faa8b41129a9dd89c45
2018-06-03remove deprecated "dest" config option from config filesHarald Welte1-1/+0
Change-Id: I1073846c04a8466f2ccf501e27cf152df09042c5
2018-04-24jenkins.sh: have one common function to collect logsNeels Hofmeyr1-5/+1
To remove code dup and prepare a change to where logs are written, add collect_logs() to jenkins_common.sh and call that from each jenkins.sh after the tests are done. The 'rm -rf' is already done before a test starts. No need to do that again after each test. Change-Id: I5d8472ec36b07c828685b1bd7718e31392d168a3
2018-04-17ttcn3-*-test: Remove cherry-pick of CCM related HACKHarald Welte1-1/+0
This is no longer needed as the fix for https://osmocom.org/issues/2718 has been merged to master of osmo-ttcn3-hacks Change-Id: Ia0c1c134405fdbce1c65059d705827f1a643e774 Related: OS#2718
2018-04-10ttcn3-bts-test/jenkins.sh: fix fake_trx.py pathVadim Yanitskiy1-1/+1
Change-Id: Ie9931651d477dc95c561a5ed554d5360b465d4da
2018-04-06ttcn3-bts-test: Configure BTS to have dynamic PDCHHarald Welte1-2/+2
This is required by later versions of the osmo-ttcn3-hacks BTS test suite after Change-Id I2a42531dc5555ab4772d538fda462343605b8feb Change-Id: I229000ce7609845fdf24cafe1f5ec2bfa3f507e8
2018-04-03ttcn3-bts-test: properly configure CTRL interfaceNeels Hofmeyr2-0/+3
osmo-ttcn3-hacks adds configuration of the CTRL interface in I502b4891e6720ae2fb251c03542f707880a6f728. We need proper IP addresses here for the f_ipa_ctrl_start() to work. WARNING: This commit has to be merged "at the same time" as I502b4891e6720ae2fb251c03542f707880a6f728 or the jenkins ttcn3-bts-tests will fail. a) if we want to set a modulepar mp_ctrl_ip here, it needs to be added to osmo-ttcn3-hacks. b) if we have the f_ipa_ctrl_start() in osmo-ttcn3-hacks, we need to configure the proper IP and bind interface here, or all tests will fail because f_ipa_ctrl_start() cannot connect. Change-Id: I1ec86b157ebd46bf622a0ca51eba225f15c99fbb
2018-03-18ttcn*test: use log_merge.sh to generate per-testcase merged logsHarald Welte1-1/+1
2018-03-13bts-test: Change logging to file so we get BTS/BSC logs as test resultHarald Welte2-4/+4
2018-03-13Add *.control to the [EXECUTE] statement of all ttcn3 test suitesHarald Welte1-0/+1
In osmo-ttcn3-hacks, we have removed the *.control from the *.default files, so let's add it here in the config files. You can now change the tests to be executed by simply editing the config here.
2018-03-01Add osmo-bts-test + dependenciesHarald Welte7-0/+404
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-25 14:57:47 +0000