These are public posts tagged with #expect. You can interact with them if you have an account anywhere in the fediverse.
https://www.europesays.com/uk/236814/ The Rise of Temporary Jobs in London: What to Expect #Britain #England #expect #GreatBritain #in #jobs #london #of #rise #temporary #the #to #UK #UnitedKingdom #what
https://www.europesays.com/2185000/ Why does Brussels expect less immigration and fewer jobs, but also less unemployment? #also #And #Brussels #But #does #Economy #EconomyOfEU #EconomyOfTheEU #EUEconomy #Europe #expect #fewer #Immigration #jobs #less #unemployment #why
In Swift 6.2, Swift Testing can validate process termination!
If your code uses `fatalError` or `precondition`, you can validate this with `#expect(processExitsWith:)`.
Check that an expression causes the process to terminate…
Apple Developer Documentation@finestructure @cocoaphony Is the code in the test function actually throwing an error or just calling #expect() (or some such)? If a test function throws an error, it's just thrown naturally until something catches it. If code in Swift Testing catches it (which happens outside the context of test-scoped traits) then the error is recorded as a test issue.
#SouthernAfrica #Africa #Africans #budget #business #BusinessandFinance #currentevents #Economy #expect #governance #news #politics #South #SouthAfrica #SouthernAfrica #sports #trade #travel #Southern Africa What South Africans Can Expect from the 2025 Budget
https://tinyurl.com/27ze4zvx
Finance Minister Enoch Godongwana has presented his…
Axadle | Stay Informed with Horn of Africa Headlines@danielkasaj @nicklockwood @vanvoorden I was trying to understand why this is better than just putting the try before the #expect() as I am doing. I understand now though - the issue is that putting try outside the expect sometimes won't compile (in my case it does, so I think it doesn't matter in this case)
@nicklockwood @vanvoorden you don’t have to worry if it’s before #expect or inside the parentheses
@nicklockwood wait a second, #expect doesn’t require a throw. I mixed it up with something else. Yeah if the expression inside it could throw, I’d expect to put “try” inside the #expect.
@danielkasaj @vanvoorden how does the output differ in this approach vs putting the try before the #expect?
@cocoaphony @dimsumthinking note that comments added to @Test and #expect macros are captured as metadata and are printed in logs on test failures. So just keep doing what you’re doing.
#Trudeau advierte que #Trump quiere #anexionar #Canadá para hacerse con sus #minerales #críticos
Did you #expect it was #love ? Nope
+ #Ukrainian #rare #earths
+ #Greenland #rare #earths / #minerals
+ etc..
Did you expect it was for " #national #security " ?
https://efe.com/mundo/2025-02-07/trump-anexion-canada-minerales-criticos/
Toronto (Canadá) (EFE).- El primer ministro canadiense,…
EFE Noticias@carnage4life that's the point, no? To stir up the #crazies with having to deal with the #demons #trapped inside theirs? I #imagine they #expect their #free #peepShow to be of their choosing too, but #God doesn't #operate that way!
Can we ALL get a little more #private once again?
Bring #Privacy Back Again
There, that's a #slogan worth a #chant
The rest can #buggerOff
20. Expect — But wealth wasn’t what she expected from him …
This year, I’ll tell the story of the Human Chair and how it arrived in Lady d’Arcy seminary. I’ll use my own words list.
#art #fanart #artwork #artoftheday #nautilebleu #owncharacter #inktober #horror #expect #spooky #creepy #weird #humanchair #artistsupportingartists #characterart #fediart #mastodonart #mastoart #creativetoots
Der Bug in iOS 18 erwähnt in der gestrigen Freakshow (ja sehr nerdig, aber Leute haben gefragt)
@Test func testConvertUnorderListHTMLToPlainText() {
let htmlString = "<ul><li>Test</li><li>Test2</li></ul>"
let decoded = try? NSAttributedString(data: Data(htmlString.utf8), options: {[.documentType: NSAttributedString.DocumentType.html, .characterEncoding: String.Encoding.utf8.rawValue] }(), documentAttributes: nil)
#expect(decoded?.string == "\t•\tTest\n\t•\tTest2\n")
}
@griotspeak you can put the tests in the same file as the types they’re testing you know!
struct Foo { private var bar: Bar }
#if ENABLE_LITERATE_TESTING
internal import Testing
extension Foo {
@Suite(“Foo Tests”)
fileprivate struct Tests {
@Test
func baz() {
#expect(Foo().bar.isBazzy)
}
}
}
#endif
anything but @\testable!
@throwspace Thanks, I think I get what you're saying. I was hoping for a way that the new parameterized tests to pass the source location of the parameter instances (maybe as an extra argument?).
The failure message shows the failing argument at the #expect but not at the original source location.
I had put together https://github.com/wwake/EgTest for parameterized testing with XCTest and am hoping I can retire it.
I don't see a macro to get a SourceLocation to map (as #file/#line do).
Thanks
EGTest - a package for parameterized testing in Swift…
github.com