Ilya,
I would love to see both of your suggestions implemented, but you may need
to submit a swift-evolution proposal for them. I think Apple employees
maintaining swift-corelibs-xctest would have a better idea of whether your
proposals would be accepted by the core team. (+cc Brian Croom).
I thi
Hey Ilya,
I'm glad you're thinking about how to use corelibs-xctest on mobile
devices. I'd like to prepare it for Android as well, and I think there's a
lot of overlap here.
> This proposal is because Swift has very poor reflection at the moment. So
I suggest creating a generator (pre-build scrip
Dan,
Unfortunately, the method that Xcode uses to display tests in the test
navigator is private. We are unable to implement that functionality in
swift-corelibs-xctest. If you'd like to see this working, please file an Apple
Radar that asks the Developer Tools team to document how this system w
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
Foundation
Speaking of JIRA tasks, I remembered this morning that the versions of
swift-corelibs-foundation and swift-corelibs-xctest expose public API that
does not exist in their Apple counterparts. This is because of a bug in the
linker that prevents us from marking attributes as private:
- https://bugs.s
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 stil
Thanks for the heads up, Tony!
(+cc corelibs-xctest release manager Mike Ferris)
Just to confirm, we are not resolving https://bugs.swift.org/browse/SR-710,
"Generate XCTestCaseProvider entries on Linux", in time for the Swift 3
release. Is this correct?
- Brian Gesiak
On Fri, Jul 29, 2016 at 2
I received some feedback from Paulo Faria that I’d like to share here:
Is there a way to change the performance test baselines by code? I can’t
find a way to do it today. So my question would be, why can’t we set the
baselines by code? Is it because we need a different baseline for each
different
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 p
I received some feedback on this proposal from Ankit Aggarwal, which
centered on how developers would edit and update their baseline metrics.
Here’s what I’m envisioning specifically:
Two new command-line options for swift test
1. swift test --performance-metrics . This is a path to a
direct
Hello corelibs-dev and build-dev,
Back in May, Brian Croom implemented performance testing in
swift-corelibs-xctest:
https://github.com/apple/swift-corelibs-xctest/pull/109
I’d love to see Swift developers use this feature to measure the
performance of their code. I think we’ll need to add functi
accordingly.
Until the next snapshot, an alternative to building your own toolchain would be
to check out an older commit of Foundation which still builds with the compiler
in the snapshot toolchain, since XCTest doesn't depend on any of the more
recent Foundation changes. I've had s
>>>>>> Hi Brian Croom,
>>>>>>
>>>>>> Thanks for the quick response. I deleted the entire build directory
>>>>>> now. Initiated a new build. Fingers crossed...
>>>>>>
>>>>>> Will update the s
at 8:32 AM, Madhu Samuel
>>>> wrote:
>>>>
>>>>> Wow, that was a quick response. Thanks Brian Gesiak and Brian Croom.
>>>>>
>>>>> My first quick attempt using build-toolchain script to build my own
>>>>> tool
commit of Foundation which still builds with the compiler
in the snapshot toolchain, since XCTest doesn't depend on any of the more
recent Foundation changes. I've had success using this commit:
https://github.com/apple/swift-corelibs-foundation/commit/04d4f92870652160388f1c69de3fd7bb06568
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`,
right
ob Allen via swift-corelibs-dev <
> *swift-corelibs-dev@swift.org* >
> To:Brian Gesiak <*modoca...@gmail.com* >
> Cc:Swift Core Libs <*swift-corelibs-dev@swift.org*
> >
> Date:30/05/2016 08:08
> Subject: Re: [swift-corelibs-dev] libdispatch on Linux, or C++
> std::
n...@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
>
>
> On 30 May 2016, at 0
Hello all!
I'm working on https://bugs.swift.org/browse/SR-710, which involves porting
SourceKit to Linux. SourceKit contains a handful of references to
libdispatch symbols.
I have two questions:
1. Could someone share a set of instructions to build
swift-corelibs-libdispatch on Linux? I'm using
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
Madhu,
Thanks for the report!
The main difference between the build scripts (which use xcodebuild) and using
Xcode itself is the version of Swift that is used. The build scripts build a
Swift 3.0 compiler, then use that to build XCTest. When using Xcode directly,
you need to select a recent Swif
Hey Jordan,
Thanks for the email! Very good point -- and I definitely felt weird
assigning "Swift 3" labels to tasks, considering it's not up to me to
decide what goes into Swift 3 or not. Still, I think it's helpful to see,
at a glance, what are the time-sensitive tasks for a given project.
Ideal
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
Hello all!
If you're like me, you might be curious how Core Libraries like
swift-corelibs-xctest are doing with regards to the looming Swift 3.0
release. Well, wonder no more -- this handy JIRA dashboard has the
information you need:
https://bugs.swift.org/secure/Dashboard.jspa?selectPageId=10408
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 swift(
Hello all,
I've been referring to the project hosted at
https://github.com/apple/swift-corelibs-xctest as
"swift-corelibs-xctest", and the project shipped alongside Xcode 7.2
as "Apple XCTest".
What are the canonical names for these projects? I'd like to agree on
common terminology to avoid confu
Thanks for the head's up! Conversely, I imagine that for many people, holidays
from work are precisely the time to contribute! :)
- Brian Gesiak
On Thu, Dec 17, 2015 at 9:03 AM -0800, "Tony Parker via swift-corelibs-dev"
wrote:
Hello fellow contributors,
As you are aware, we are
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
I sent up another attempt for this:
https://github.com/apple/swift-corelibs-xctest/pull/10
Based on the discussion in that pull request, I'm now exploring using lit to
test the XCTest output.
Rather than asking contributors to install lit via the Python Package Index, I
was considering using th
29 matches
Mail list logo
