Update Testing documentation

[alemohamad]

Following the issues #1038 and #594, this proposal suggests updating the Testing documentation to include Swift Testing as an alternative to XCTest.

[MahdiBM]

This looks good but not sure if we want to replace the XCT docs, or add a new one for Swift Testing.

[0xTim]

I agree with @MahdiBM - we should keep the old XCTVapor docs but put a warning telling people they should choose VaporTesting unless they have a reason not to

[alemohamad]

I understand. In my opinion we should be promoting the Swift Testing option first and then add a note about the XCTest framework. I think that having a complete example with the new framework can be another way of encouraging its usage.

What do you prefer? Maintain the XCTest with a note about Swift Testing or the other way around?

[0xTim]

What do you prefer? Maintain the XCTest with a note about Swift Testing or the other way around?

Swift Testing first, XCTest at the bottom

[alemohamad]

@0xTim now that we are reviewing the Testing page, should we look at this issue #865 ? We can remove the text about precondition failure, if this is resolved. Let me know.

[0xTim]

@alemohamad you still need to call it to shutdown services, but if you use the withApp stuff then it's done for you

[0xTim]

Thanks!

[alemohamad]

@0xTim sorry, tapped on cancel the auto-merge.