From: Elif Aslan <elas@linux.vnet.ibm.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] added vmcp test
Date: Mon, 4 Mar 2019 10:12:47 +0100 [thread overview]
Message-ID: <20190304091247.2057-1-elas@linux.vnet.ibm.com> (raw)
---
runtest/s390x_tests | 2 ++
testcases/commands/vmcp/README.md | 29 ++++++++++++++++++
testcases/commands/vmcp/vmcp_m.sh | 49 +++++++++++++++++++++++++++++++
3 files changed, 80 insertions(+)
create mode 100644 runtest/s390x_tests
create mode 100644 testcases/commands/vmcp/README.md
create mode 100644 testcases/commands/vmcp/vmcp_m.sh
diff --git a/runtest/s390x_tests b/runtest/s390x_tests
new file mode 100644
index 000000000..0c2bf05a5
--- /dev/null
+++ b/runtest/s390x_tests
@@ -0,0 +1,2 @@
+# Those tests are designed to be executed in s390x environment (zVM or LPAR)
+vmcp vmcp_m.sh
diff --git a/testcases/commands/vmcp/README.md b/testcases/commands/vmcp/README.md
new file mode 100644
index 000000000..7ff79a89c
--- /dev/null
+++ b/testcases/commands/vmcp/README.md
@@ -0,0 +1,29 @@
+# vmcp tool and module test
+
+The tool allows Linux users to send commands to the z/VM control program (CP).
+The normal usage is to invoke vmcp with the command you want to execute.
+
+## Getting Started
+
+The test case contains one shell script:
+
+- **vmcp_m.sh**: *basically executes the vmcp tool with different parameters and verifies that
+ output and exitcodes are as expected*
+
+## Prerequisites
+
+z/VM guest must be prepared to be populated with guest Linux OS.
+
+## Running the tests manually
+
+Transfer the scripts to the target system and run:
+
+./vmcp_m.sh
+
+## Versioning
+
+Tested already on SLES 12 SP3
+
+## License
+
+The files in this directory are licensed under the GPL v2+ license.
diff --git a/testcases/commands/vmcp/vmcp_m.sh b/testcases/commands/vmcp/vmcp_m.sh
new file mode 100644
index 000000000..f33b6fc71
--- /dev/null
+++ b/testcases/commands/vmcp/vmcp_m.sh
@@ -0,0 +1,49 @@
+# SPDX-License-Identifier: GPL-2.0-or-later
+
+#!/bin/sh
+
+TST_CNT=2
+TST_TESTFUNC=vmcp_main
+TST_USAGE=usage
+. tst_test.sh
+
+usage()
+{
+cat << EOF
+usage: $0
+
+OPTIONS
+EOF
+}
+
+vmcp_run()
+{
+
+ $2
+ if [ $? -eq $1 ]; then
+ tst_res TPASS "'$2' returned '$1'"
+ else
+ tst_res TFAIL "'$2' did not return '$1'"
+ fi
+}
+
+vmcp_main1()
+{
+ echo "verifyBasicVMCPCommands"
+ vmcp_run 0 "vmcp --version";
+ vmcp_run 0 "vmcp --help";
+ vmcp_run 0 "vmcp -v";
+ vmcp_run 0 "vmcp -h";
+ vmcp_run 0 "vmcp q dasd";
+}
+
+vmcp_main2()
+{
+ echo "verifyErrorCondition"
+ vmcp_run 4 "vmcp -L"
+ vmcp_run 4 "vmcp -m q dasd"
+ vmcp_run 1 "vmcp dasddasddasd"
+}
+
+
+tst_run
--
2.17.2 (Apple Git-113)
next reply other threads:[~2019-03-04 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 9:12 Elif Aslan [this message]
2019-03-04 13:53 ` [LTP] [PATCH] added vmcp test Cyril Hrubis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190304091247.2057-1-elas@linux.vnet.ibm.com \
--to=elas@linux.vnet.ibm.com \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox