I like to put the expected first, which leans towards the convention of "keep function parameters that are more known or less likely to be variable to the left".
Something to also consider, hamcrest macros go the other way:
assert_that!(actual, contains(vec!["a", "b", "c"]));