Open brentsimmons opened 3 months ago
I have no plan yet. :)
Oh okay, then we can postpone this.
@ankushkushwaha , I would love to work on this issue.
I recently added Swift Testing to 2 packages.
Honestly, it shouldn't matter very much where we start since converting one test from XCTest to Swift Testing doesn't change the API, and therefore shouldn't break any other tests.
But I think the Parser module is a good place to start, since it's a very well understood problem space with lots of resources.
However it is worth noting that Swift Testing, is Swift 6+ only. So on my projects, I have to use a Package@swift-6.0.swift
in order to use Swift Testing. This may be less of an issue after Xcode 16 officially comes out next week and more people have the Swift 6 compiler by default.
Just to highlight potential benefits, I found a ton of code reuse on tests here: https://github.com/Ranchero-Software/NetNewsWire/blob/main/Modules/Parser/Tests/ParserTests/HTMLMetadataTests.swift
There are 12 tests, but with Swift Testing we only need about 3. We could reduce tests using parameterized testing. There could be 3 tests, parseSite
, performance
and loadImage
, and these tests could be reused for each website.
Okay, sounds interesting to me. @brentsimmons is the correct person to give permission to move forward for this task :)
It‘s going to be a while before we start this — we’re working on the 6.2 milestone and using Xcode 15.4 for now.
Cool. @ me whenever you're ready. I'd love to work on this.
Hi @brentsimmons can you please provide more description, for example what is the plan? which modules/classes we can start first?