Things to snapshot about swift-snapshot-testing HOT 7 CLOSED

Do you think it's possible to snapshot generated interface of a swift file?
The goal is to see if we can compare public interface of a file and see if it has changed ?

from swift-snapshot-testing.

@Sherlouk @stephencelis Thanks for the replies.

For .swiftinterface it will be for Swift 5.1 for module stability.

For the memory and CPU snapshot we could use task_info API ?

from swift-snapshot-testing.

Should we consider snapshotting memory, cpu, network (volume of data transmitted) and disk usage ?

from swift-snapshot-testing.

For URL is there a reason you wouldn't simply compare absoluteString also maybe an option to compare URLComponents (nicer breakdown vs URL on it's own)?

On the public interface, it sounds like an interesting idea but I'm not actually sure how that would be done. Do you have any pointers? I partnered a friend at work when he was working on Guise which creates a public interface document as part of a run script - not sure how the connection could be made!

from swift-snapshot-testing.

Hey @mackoj missed your earlier comments, sorry!

Should we consider snapshotting memory, cpu, network (volume of data transmitted) and disk usage ?

Sounds interesting! Thoughts on how to track this kind of thing, though?

Do you think it's possible to snapshot generated interface of a swift file?
The goal is to see if we can compare public interface of a file and see if it has changed ?

Not sure! Maybe with SwiftSyntax or SourceKitten! Would be an interesting tackle.

Hey @Sherlouk!

For URL is there a reason you wouldn't simply compare absoluteString also maybe an option to compare URLComponents (nicer breakdown vs URL on it's own)?

I'm not sure if @mbrandonw had some more ideas for what to do with URL. 🤔 Right now a .dump works well to do basically what absoluteString would do.

from swift-snapshot-testing.

Do you think it's possible to snapshot generated interface of a swift file?

In Swift 5 a .swiftinterface file is created (link) which is a textual representation of the public/open interface for the library.

Should be fairly doable to use __XCODE_BUILT_PRODUCTS_DIR_PATHS to load that file - snapshot it locally with the test and run a comparison.

(Should say I'm not running Swift 5 at the mo otherwise I'd jump on prototyping this, sounds like an interesting idea)

from swift-snapshot-testing.

I'm doing some spring cleaning and am closing issues that don't have an obvious fix, like this one 😄 Great discussion and ideas in this thread, though. When GitHub Discussions rolls out we should consider it as a forum for exploring new snapshot strategy ideas. Till then, if you come up with something you'd like to PR, we'd love to see it!

from swift-snapshot-testing.