add test hints

[lijunchen]

moon test is different from other modes, this PR only adds hints for test

[peter-jerry-ye-code-review]

Issues Detected in the Provided git diff Output

1. Typo in Variable Name:

   • In the file crates/moon/tests/test_cases/mod.rs, there is a repeated variable name failed in the println! statement. The variable failed is used twice, which could be a typo or an unintended repetition. It might be better to use different variable names for clarity.

   println!(
       "Total tests: {}, passed: {}, failed: {}.{}",
       if total > 0 {
           total.to_string().blue().to_string()
       } else {
           total.to_string()
       },
       if passed > 0 {
           passed.to_string().green().to_string()
       } else {
           passed.to_string()
       },
       if failed > 0 {
           failed.to_string().red().to_string()
       } else {
           failed.to_string()
       },
       backend_hint,
   );

2. Unused Variable display_backend_hint:

   • In the file crates/moon/src/cli/test.rs, the variable display_backend_hint is declared but not used in the run_test_internal function. This variable is meant to provide a hint about the backend, but it seems to be unnecessary in the current context.

   fn run_test_internal(
       cli: &UniversalFlags,
       cmd: &TestSubcommand,
       source_dir: &Path,
       target_dir: &Path,
       display_backend_hint: Option<()>, // This variable is not used
   ) -> anyhow::Result<i32> {
       // Function body
   }

3. Inconsistent Test Output:

   • In the file crates/moon/tests/test_cases/mod.rs, the test output format changes from a simple count to a more detailed format that includes the backend hint. This change might break existing tests or expectations in the test suite. It's important to ensure that all test cases are updated to match the new output format.

   // Old format
   Total tests: 1, passed: 0, failed: 1.
   
   // New format
   Total tests: 1, passed: 0, failed: 1. [wasm]

Suggestions

1. Fix Typo:

   • Consider renaming the repeated failed variable to avoid confusion. For example, use failed_count or failures.

2. Remove Unused Variable:

   • If the display_backend_hint variable is not used within the function, it should be removed to avoid confusion and potential bugs.

3. Update Test Cases:

   • Ensure that all test cases and expectations are updated to match the new output format, including the backend hint. This will maintain consistency and prevent test failures due to mismatched output expectations.

[Young-Flash]

could we remove if we put backend into end ?

      Total tests: 0, passed: 0, failed: 0. [wasm]
      Total tests: 0, passed: 0, failed: 0. [wasm-gc]
      Total tests: 0, passed: 0, failed: 0. [js]

[lijunchen]

In the current situation, this is a good idea.