Generic XCTest assertions produce vague failure messages. Building custom assertion helpers with #filePath and #line preserves accurate failure locations while producing much clearer diagnostics. Small technique with outsized value for test quality.

🔗: https://qualitycoding.org/swift-test-assertions/ by Jon Reid (@qcoding)

#Swift #Testing #iOSDev

Can anyone point me to an online Java compiler which runs the JDK on Windows? I only find Linux systems.

I would be particularly interested in what

java.nio.file.Path.of("a/b/c")

returns on a Windows system. My hunch is that it is the same as

java.nio.file.Path.of("a\\b\\c")

because the forward slash, afair, also works as a path separator. Or is the forward slash merely a no-go character like ':' and many others?

#java #windows #filepath #filename

XCTest pro tip: if you create your own assert functions, add file: and line: parameters to see where the error „really" happened. Example from my UITableView assertion DSL:

@discardableResult
func assertNumberOfSections(_ number: Int, file: StaticString = #filePath, line: UInt = #line) -> Self {
XCTAssertEqual(
tableView.numberOfSections,
number,
file: file, line: line
)
return self
}