I use the following to build Foundation and XCTest, then run the XCTest tests:
swift $ utils/build-script --preset corelibs-xctest
The XCTest.xcworkspace is also capable of building and testing. Open it, select
the XCTest scheme, and build with ⌘B. You should also be able to build the
I think a future release is prudent, for the following reasons:
1. swift-corelibs-xctest requires users to list each of their tests in an
`allTests` static property. However, this isn't source-incompatible with
Darwin XCTest. A developer could include the list on Darwin, and their
tests would
Hi, it’s me again. :)
I figured out how we can do this on Darwin: by using .xctestconfiguration
files.
SwiftPM performance tests on Darwin, using XCTestConfiguration files
Xcode passes all sorts of variables to XCTest by specifying the
XCTestConfigurationFilePath=/path/to/an.xctestconfiguration
tus 1, aborting
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Jun 21, 2016 at 12:35 PM, Madhu Samuel <madhusam...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Brian Croom,
>>>>>>
>>
Excellent work! I've been enjoying watching all the WWDC livestreams. :)
About the changes to swift-corelibs-xctest: you mean simply using the new
Foundation APIs, correct? I don't imagine we'll be changing the XCTest API
very much -- that is, we won't be renaming `XCTestCase` to `TestCase`,
Date:30/05/2016 08:08
> Subject:Re: [swift-corelibs-dev] libdispatch on Linux, or C++
> std::async?
> Sent by: *swift-corelibs-dev-boun...@swift.org*
> <swift-corelibs-dev-boun...@swift.org>
> --
>
>
>
>
> H
:swift-corelibs-dev-boun...@swift.org
> --
>
>
>
> Hi,
>
> For what it's worth, I can't get the master branch to build either, but I
> can get the experimental/foundation branch to build.
>
> Regards,
>
> Rob
>
>
>
Madhu,
Oy, my bad -- I only just noticed you put the toolchain version at the bottom
of your original email.
It's possible the May 9th toolchain is already too old to build XCTest. I'll
double-check myself. In the meantime, you may want to try building your own
toolchain and using that.
- Brian
ven clearer instructions, and labeled as a starter task...
>
> - Brian Gesi
>
>
> On 23 May 2016, at 22:41, Tony Parker via swift-corelibs-dev <
> swift-corelibs-dev@swift.org> wrote:
>
> This is slick!
>
> I would love to have one for Foundation too (although my understand
I noticed the folks at IBM were also doing platform checks when using the
corelibs-xctest APIs. I created https://bugs.swift.org/browse/SR-1215 to
track the issue.
corelibs-xctest is small enough that we may want to consider providing
*both* Swift 2.2 and Swift 3 APIs, perhaps behind a `#if
I've submitted https://github.com/apple/swift-corelibs-xctest/pull/14
as another attempt at this.
Take a look at the pull request message for details. Turns out I'd
overlooked another dependency: nearly all lit tests use FileCheck,
which means to run the tests developers will need to specify that
11 matches
Mail list logo
