Re: [swift-corelibs-dev] [xctest] Who tests the tests?

2015-12-04 Thread Mike Ferris
One possible direction to consider which would be more consistent with our goals this year for API-compatibility would be to look into implementing XCTestObserver. Mike > On Dec 3, 2015, at 8:03 PM, Tony Parker wrote: > > Hi Brian, > >> On Dec 3, 2015, at 3:45 PM, Brian Gesiak >

Re: [swift-corelibs-dev] [xctest] Who tests the tests?

2015-12-04 Thread Mike Ferris
atform tests into suites that include features that Obj-C XCTest has >> that we will probably not add to the Swift one (e.g., UI testing). > > Absolutely agree. Still, once we have regression tests in place, I'd > love to start a conversation about whether we could provide a Obj-C &g

Re: [swift-corelibs-dev] [xctest] Removing outliers from performance tests

2015-12-13 Thread Mike Ferris via swift-corelibs-dev
I think that there’s a lot of room for improvement in how we measure and analyze perf test results. And I like some of your ideas of adaptive numbers of runs and what to do with outlier results, etc… that you presented below. We would very much like to not diverge the API of the CoreLibs XCTest

Re: [swift-corelibs-dev] Upcoming holiday schedule

2015-12-18 Thread Mike Ferris via swift-corelibs-dev
I will also be out starting tomorrow through the end of the month which means XCTest will get little coverage during that time. Mike > On Dec 17, 2015, at 9:18 AM, Philippe Hausler via swift-corelibs-dev > wrote: > > I will probably be around a bit more than Tony over the break; I will try to

[swift-corelibs-dev] Swift3 rewriting for XCTest APIs

2016-04-15 Thread Mike Ferris via swift-corelibs-dev
Swift3 rewriting for XCTest APIs For the most part, the automatic heuristics seem to be doing the right things for Xcode’s XCTest. We have identified a few cases where we should perhaps discuss doing a little extra. Almost everything seems like it imports reasonably according to the API guidel