-
Notifications
You must be signed in to change notification settings - Fork 183
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
add GitHub Actions for integration test #833
add GitHub Actions for integration test #833
Conversation
20分も待たないといけないのは、ちょっと辛いかな?と思いました。 |
@kazuminn |
- remove macos from matrix
後でデフォルトで[profile.release]配下のcodegen-units = 1を消しましょうか? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
一旦マージしましょう。
早速マージいただき、ありがとうございます🙇 |
hayabusa-sample-evtx
に対して、ビルド後のhayabusa
でコマンド実行をテストするworkflowを作成してみました!すみません、このworkflowがmainマージ後にしか実行できないため、大変恐縮なのですが、
以下fukusuketリポジトリにて実行した内容で、もし差し支えなければマージいただけると幸いです🙇
What Changed
How to use
Integration Test
in left menu.Run worflow
.Run workflow
Integration test contents
Trigger
When I run the workflow manually.
OS
Run the tests on the following two OS in parallel.
Command
Run the following 13 commands, and if the return code is not 0, the workflow will fail.
help
update-rules -q
csv-timeline -d ../hayabusa-sample-evtx -o out.csv -q
csv-timeline -d ../hayabusa-sample-evtx -o out-s.csv -P super-verbose -q
json-timeline -d ../hayabusa-sample-evtx -o out.json -q
json-timeline -d ../hayabusa-sample-evtx -o out-s.json -P super-verbose -q
json-timeline -d ../hayabusa-sample-evtx -o out.jsonl -q -J
logon-summary -d ../hayabusa-sample-evtx -q
metrics -d ../hayabusa-sample-evtx -q
pivot-keywords-list -d ../hayabusa-sample-evtx -o p.csv -q
level-tuning --level-tuning ./rules/config/level_tuning.txt -q
set-default-profile -q
list-contributors -q
Execution time
It takes about 20 minutes to run all tests.(About 10 minutes build time ... :( )
Result
Failed
If the command results has one or more non-zero return codes.
![スクリーンショット 2022-12-09 23 59 26](https://user-images.githubusercontent.com/41001169/206732209-569403b2-53a6-4f97-bec4-14eef059a637.png)
Succeded
If the return code is all 0 in the result of the commands.
![スクリーンショット 2022-12-10 0 04 23](https://user-images.githubusercontent.com/41001169/206732236-068436f3-75e3-4f0d-8e04-7b9a4e63b11b.png)
Note
Currently, I created test cases based on the specifications after subcommand implementation
(So currently running the workflow on the main branch will fail.)