When writing unit tests, when should I override `invokeTest`?

In the context of writing unit tests, overriding invokeTest is not typically necessary when using Swift Testing, as discussed in the Meet Swift Testing session. Swift Testing introduces a new approach that integrates seamlessly with Swift concurrency and provides various features like async/await support, actor isolation, and traits for specifying test information.

If you are using XCTest, invokeTest might be overridden in more advanced scenarios where you need to customize the execution of test methods, but this is not a common practice for most unit tests. Instead, Swift Testing encourages using the test attribute to denote test functions explicitly, which simplifies the process and reduces the need for such overrides.

For more details on how Swift Testing and XCTest relate, you can refer to the Meet Swift Testing session.