make vty-transcrip-test: use $VTY_TEST var like osmo-bsc

Adopt the same way to run manual vty transcript tests as in
osmo-bsc/test/Makefile.am.

There are different ways to select a specific test to run in osmo-bsc and here
in osmo-msc. The osmo-bsc way is more convenient when building outside the src
tree, because it does not need the full absolute path of the test file.

Change-Id: If1e2abfa321a5e9fb60358d1f0e4e448b33184af
changes/69/18969/2
Neels Hofmeyr 2 years ago committed by laforge
parent 83cf10c8a6
commit 1139ca352b
  1. 5
      tests/Makefile.am

@ -71,6 +71,9 @@ endif
$(srcdir)/vty_test_runner.py -w $(abs_top_builddir) -v
rm -f $(top_builddir)/sms.db
# Run a specific transcript test with: 'make vty-transcript-test VTY_TEST=osmo-msc.vty'
VTY_TEST ?= *.vty
# To update the VTY script from current application behavior,
# pass -u to vty_script_runner.py by doing:
# make vty-transcript-test U=-u
@ -78,7 +81,7 @@ vty-transcript-test:
osmo_verify_transcript_vty.py -v \
-n OsmoMSC -p 4254 \
-r "$(top_builddir)/src/osmo-msc/osmo-msc -c $(top_srcdir)/doc/examples/osmo-msc/osmo-msc.cfg" \
$(U) $${T:-$(srcdir)/*.vty}
$(U) $(srcdir)/$(VTY_TEST)
rm -f $(builddir)/sms.db
# don't run multiple tests concurrently so that the ports don't conflict

Loading…
Cancel
Save