Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Guest test executor refactoring #151

Merged
merged 2 commits into from
Dec 8, 2023

Conversation

hongyuni
Copy link
Contributor

@hongyuni hongyuni commented Dec 6, 2023

No description provided.

refactoring guest.test_executor into $FEATURE based general
implementation, distribute $TESTCASE based feature level test_execution
to $FEATURE/$FEATURE.test_executor.sh

[Test Components] tdx
[Test Types] any
[Supported Devices] spr,emr,gnr,srf

Signed-off-by: Hongyu Ning <[email protected]>
@hongyuni
Copy link
Contributor Author

hongyuni commented Dec 8, 2023

Hi @ysun , would you help on this guest-test code architecture refactoring review, it's done based on Rex Zhang's new guest-test feature adding proposal, hopefully we could support new features being added easily and clearly from more contributors like Rex start from this new refactoring done.

@ysun
Copy link
Contributor

ysun commented Dec 8, 2023

Hi @ysun , would you help on this guest-test code architecture refactoring review, it's done based on Rex Zhang's new guest-test feature adding proposal, hopefully we could support new features being added easily and clearly from more contributors like Rex start from this new refactoring done.

Sure, sorry I missed this PR. I'll do it ASAP.

SCRIPT_DIR="$( cd "$( dirname "$0" )" && pwd )"
echo "$SCRIPT_DIR"
else # bypass above execution in case of being sourced
ehco "guest.test_executor.sh being sourced"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: ehco -> echo

echo "$SCRIPT_DIR"
# exec only if script being executed
if [ "${BASH_SOURCE[0]}" -ef "$0" ]; then
SCRIPT_DIR="$( cd "$( dirname "$0" )" && pwd )"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, are the quotation marks really necessary? Or is it for coding style checking?
Why not SCRIPT_DIR=$( cd $( dirname "$0" ) && pwd ) ?


###################### Variables ######################
## common variables example ##
SCRIPT_DIR_LOCAL="$( cd "$( dirname "$0" )" && pwd )"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same question as the previous one about the quotation marks.


###################### Do Works ######################
## common works example ##
cd "$(dirname "$0")" 2>/dev/null || exit 1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's my concern about the quote marks, what do you really want to quote? Here are "$(dirname " and ")". Are they correct?

update previous osv_sanity implementation reference based on
test_executor refactoring

[Test Components] tdx
[Test Types] func
[Supported Devices] spr,emr,gnr,srf

Signed-off-by: Hongyu Ning <[email protected]>
@hongyuni hongyuni force-pushed the guest_test_executor_refactoring branch 2 times, most recently from a360f20 to 3441275 Compare December 8, 2023 08:32
@ysun ysun merged commit 18e9a89 into intel:main Dec 8, 2023
1 of 2 checks passed
@ysun
Copy link
Contributor

ysun commented Dec 8, 2023

Thank Hongyu for the quick response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants