test(integration): add tests for standalone arguments handling

[whyang9701]

This pull request adds a test to check that the .js file comes before the CLI options. As issue 30334 mentioned.

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

Walkthrough

The standalone_args test in the integration test suite has been enhanced to validate argument forwarding behavior. Three compile invocations now include a trailing -- separator with forwarded arguments, and a new assertion verifies the compiled executable correctly echoes these forwarded arguments.

Changes

Cohort / File(s)	Change Summary
Test argument forwarding enhancement tests/integration/compile_tests.rs	Updated standalone_args test block to include argument forwarding with -- separator across three compile invocations; added new assertion to verify compiled executable echoes forwarded arguments; updated expected output accordingly.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Single file with test-only changes
• Repetitive pattern applied consistently across multiple invocations
• New assertion follows existing test conventions

Poem

🐰 Hops through tests with glee so bright,
Arguments forward, now passing right,
Dashes and separators all aligned,
Echo and verify, perfectly designed! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding tests for standalone arguments handling, which matches the actual modifications to the integration test.
Description check	✅ Passed	The description is related to the changeset, mentioning testing for .js file ordering before CLI options as referenced in issue 30334, which aligns with the argument forwarding test additions.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

tests/integration/compile_tests.rs (1)

98-118: Consider adding a comment to clarify the purpose of the second compile cycle.

The second compile+run cycle tests that the --output flag can appear in different positions relative to the source file, which is valuable for ensuring robust argument parsing. A brief comment would make this intent explicit.

+ // Test with --output flag after the source file to ensure argument order flexibility
  context
    .new_command()
    .args_vec([

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3c0f289 and fba1206.

📒 Files selected for processing (1)

• tests/integration/compile_tests.rs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)

• GitHub Check: build libs
• GitHub Check: test release linux-x86_64
• GitHub Check: test debug linux-x86_64
• GitHub Check: test debug linux-aarch64
• GitHub Check: test debug macos-aarch64
• GitHub Check: test debug macos-x86_64
• GitHub Check: test debug windows-x86_64
• GitHub Check: lint debug windows-x86_64
• GitHub Check: lint debug macos-x86_64
• GitHub Check: lint debug linux-x86_64

🔇 Additional comments (2)

tests/integration/compile_tests.rs (2)

91-97: LGTM! Good test coverage for argument forwarding.

The test correctly verifies that:

1. Compile-time arguments passed after -- (a, b) are embedded in the binary
2. Runtime arguments (foo, --bar, --unstable) are also passed through
3. Both sets of arguments are accessible to the compiled program in the expected order

---

77-90: No issues found—test data file exists and is correctly implemented.

The file tests/testdata/compile/args.ts correctly implements argument forwarding by using Deno.args to capture and echo all arguments (both compile-time forwarded args via -- and runtime args) one per line, as expected by the test.