SwiftyMocky Verify records Swift Testing issue with source location.

Verify failed silently in Swift Testing because it does not pick up XCTAssert failure used in MockyAssert. This PR uses Swift Testing's Issue.record IF running inside a Swift Testing test. Additionally there is a bunch of changes to make the error show at the correct place in source in the editor.

Feb 14 '25 20:02 Stannieman

Great to see this, thanks @Stannieman!

@spaluchiewicz any help on getting this in is much appreciated.

Mar 21 '25 11:03 iamrado

I discovered that there is 1 thing still missing: the base64 templates in https://github.com/MakeAWishFoundation/SwiftyMocky/blob/3672eea08c7098214ac54ee26c7a7e39ea01a2f1/Sources/CLI/Core/Assets/Assets.swift still need to be updated. Do I just encode the contents of the template files?

Mar 21 '25 16:03 Stannieman

I discovered that there is 1 thing still missing: the base64 templates in https://github.com/MakeAWishFoundation/SwiftyMocky/blob/3672eea08c7098214ac54ee26c7a7e39ea01a2f1/Sources/CLI/Core/Assets/Assets.swift still need to be updated. Do I just encode the contents of the template files?

Fixed!

Mar 26 '25 10:03 Stannieman

PR updated to also include Swift Testing support for SwiftyMockyTestObserver. These failures still don't show up in the editor for some reason but at least we have full support now.

BTW: Is there a nice way to edit the templates are it it just raw dogging without syntax highlighting/autocomplete?

Mar 26 '25 14:03 Stannieman