From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: [PATCH v2 2/3] testsuite: Move test scripts to their own subdirectory
Date: Fri, 24 Mar 2023 08:01:41 +0100 [thread overview]
Message-ID: <20230324070142.27122-3-ubely@ilbers.de> (raw)
In-Reply-To: <20230324070142.27122-1-ubely@ilbers.de>
Just a cosmetic change to minimize mess in `testsuite` directory by
placing test scripts to their own subdirectory.
Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
testsuite/cibuilder.py | 2 +-
testsuite/{ => scripts}/test_example_module.sh | 0
testsuite/{ => scripts}/test_getty_target.sh | 0
3 files changed, 1 insertion(+), 1 deletion(-)
rename testsuite/{ => scripts}/test_example_module.sh (100%)
mode change 100644 => 100755
rename testsuite/{ => scripts}/test_getty_target.sh (100%)
mode change 100644 => 100755
diff --git a/testsuite/cibuilder.py b/testsuite/cibuilder.py
index 484a90b3..f37c3190 100755
--- a/testsuite/cibuilder.py
+++ b/testsuite/cibuilder.py
@@ -246,7 +246,7 @@ class CIBuilder(Test):
def run_script(self, script, cmd_prefix):
script_dir = self.params.get('test_script_dir',
- default=os.path.abspath(os.path.dirname(__file__))) + '/'
+ default=os.path.abspath(os.path.dirname(__file__))) + '/scripts/'
script_path = script_dir + script
if not os.path.exists(script_path):
self.log.error('Script not found: ' + script_path)
diff --git a/testsuite/test_example_module.sh b/testsuite/scripts/test_example_module.sh
old mode 100644
new mode 100755
similarity index 100%
rename from testsuite/test_example_module.sh
rename to testsuite/scripts/test_example_module.sh
diff --git a/testsuite/test_getty_target.sh b/testsuite/scripts/test_getty_target.sh
old mode 100644
new mode 100755
similarity index 100%
rename from testsuite/test_getty_target.sh
rename to testsuite/scripts/test_getty_target.sh
--
2.20.1
next prev parent reply other threads:[~2023-03-24 7:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 7:01 [PATCH v2 0/3] Creating custom testcases based on Isar one Uladzimir Bely
2023-03-24 7:01 ` [PATCH v2 1/3] testsuite: Check availability of script to run over ssh Uladzimir Bely
2023-03-24 7:01 ` Uladzimir Bely [this message]
2023-03-24 7:01 ` [PATCH v2 3/3] testsuite: Exmaple of custom testcase for downstreams Uladzimir Bely
2023-03-26 17:30 ` Uladzimir Bely
2023-03-31 6:48 ` [PATCH v2 0/3] Creating custom testcases based on Isar one Uladzimir Bely
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=20230324070142.27122-3-ubely@ilbers.de \
--to=ubely@ilbers.de \
--cc=isar-users@googlegroups.com \
/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