Code Actions Not Working With Async Tests

[LuisOsta]

This is what the top line of the test looks like.

 #[rstest::rstest]
    #[case::network_failure(
        create_did(),
        create_did_doc(create_did()),
        Some(Err(tonic::Status::invalid_argument("message"))),
        false
    )]
    #[case::success(
        create_did(),
        create_did_doc(create_did()),
        Some(Ok(tonic::Response::new(CreateResponse {}))),
        true
    )]
    #[case::parsing_failure(
        create_did(),
        serde_json::json!("{}"),
        None,
        false
    )]
    async fn test_create(
        #[case] did: String,
        #[case] doc: serde_json::Value,
        #[case] mock_create_response: Option<
            Result<tonic::Response<CreateResponse>, tonic::Status>,
        >,
        #[case] expect_ok: bool,
    )

Whenever we remove the async prefix to the function we have the code actions that allow us to run a specific test case. But once its async we don't have that option

[la10736]

What do you mean with code action? Are you speaking about something like gutter icon on vscode or other IDE feature?

[LuisOsta]

@la10736 I mean the code actions provided by the rust-analyzer vscode extension. It just seemed curious to me that it didn't work for async tests and thought it was an issue with rstest. As it didn't display the case by case and thought that the issue was with what the rstest macro handled the async test cases:

I've attached a photo of what it looks like normally vs async:

Normal

Async

Both tests are structured in the exact same way. The only difference is the usage of async testing as described here - https://docs.rs/rstest/latest/rstest/attr.rstest.html#async

[la10736]

Hi, you posted the same image twice :)

Anyway, that is (eventually) a rust-analyzer vscode extension's bug. I've already looked on a closed topic #120.

I guess that vscode just looking for #[test] attribute but for async tests we use #[async_std::test] attribute instead. I think that the best approach is to search an attribute where the last path segment is test but that is a vscode's chose ... not mine.