Skip to content

Releases: Quick/Quick

v7.5.0 - Pending tests are now marked as Skipped in Xcode

24 Mar 21:16
v7.5.0
Compare
Choose a tag to compare

Highlights

  • Any tests which are pended-out (using pending, xdescribe, xcontext, xitBehavesLike, or xit), OR tests which are skipped because they are not focused (that is, the other tests when you use fdescribe, fcontext, fitBehavesLike or fit) are now marked as skipped in Xcode.

Automated Changelog

  • Bump softprops/action-gh-release from 1 to 2 by @dependabot in #1274
  • Mark tested which are pended-out or not focused as skipped. by @younata in #1276

Full Changelog: v7.4.1...v7.5.0

v7.4.1

07 Mar 05:36
v7.4.1
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v7.4.0...v7.4.1

v7.4.0 - visionOS support

24 Jan 01:33
v7.4.0
Compare
Choose a tag to compare

Highlights

Autogenerated Release Notes

What's Changed

New Contributors

Full Changelog: v7.3.1...v7.4.0

v7.3.1

17 Jan 19:08
v7.3.1
Compare
Choose a tag to compare

Highlights

  • Fixes a crash in AsyncSpec caused by race condition when unsetting AsyncSpec.current.

Autogenerated Release Notes

What's Changed

Full Changelog: v7.3.0...v7.3.1

v7.3.0

17 Sep 05:10
v7.3.0
Compare
Choose a tag to compare

Highlights

  • Adds a property wrapper default initializer for TestState. Meaning the following declaration is now accepted!
@TestState var foo: Int! = 30

Thanks @tahirmt!

  • TestState now nils out the value after all afterEach blocks run, instead of in the middle of the afterEach chain. Thanks @CraigSiemens

What's Changed

  • Bump activesupport from 7.0.4.3 to 7.0.7.2 by @dependabot in #1238
  • Add property wrapper default initializer for TestState by @tahirmt in #1235
  • Bump actions/checkout from 3 to 4 by @dependabot in #1241
  • Updated TestState to remove the value after the test. by @CraigSiemens in #1240
  • Update release script to generate a carthage binary and include it in the release. by @younata in #1234

New Contributors

Full Changelog: v7.2.0...v7.3.0

v7.2.0 - TestState property wrapper

28 Jul 15:18
v7.2.0
Compare
Choose a tag to compare

Highlight

You can now use the @TestState property wrapper to automatically deconstruct test variables. For example:

describe("using TestState") {
    @TestState var subject: SomeObject?
}

Is functionally equivalent to:

describe("using TestState") {
    var subject: SomeObject?
    afterEach {
        subject = nil
    }
}

You can also specify an initial value, and TestState will act as an aroundEach: setting the wrapped variable to the value, then setting it to nil at test teardown.

describe("using TestState") {
    @TestState(1) var value: Int?

    it("is already configured") {
        expect(value).to(equal(1))
    }
}

Thanks @CraigSiemens for their contribution!

Automated Release Notes

What's Changed

Full Changelog: v7.1.0...v7.2.0

v7.1.0

06 Jul 18:50
Compare
Choose a tag to compare

Highlights

New Features

  • You can now use throw in beforeEach, justBeforeEach, and afterEach blocks.
  • Quick now suggests to XCTest that tests run in the order they are defined in.

Fixes

  • beforeEach blocks specified in configurations are now run in AsyncSpec tests.
  • xitBehavesLike(_ name: String) is now available in QuickSpec and Behavior.

Autogenerated ChangeLog

What's Changed

  • Bump danger from 9.3.0 to 9.3.1 by @dependabot in #1224
  • Ensure beforeEach in Configuration run for AsyncSpec by @junmo-kim in #1228
  • Allow beforeEach, justBeforeEach, and afterEach in Swift to throw by @younata in #1229
  • Improve documentation for installing Quick and Nimble via Cocoapods in the README. by @younata in #1231
  • Make a public xitBehavesLike(_ name: String) for SyncDSLUser by @younata in #1230
  • Attempt to run tests within a QuickSpec or AsyncSpec in the order they are defined in by @younata in #1232

New Contributors

Full Changelog: v7.0.2...v7.1.0

v7.0.2

10 Jun 00:27
Compare
Choose a tag to compare

This is a bug fix release that primarily fixes a conflict in how Nimble defines FileString and how Quick defines FileString when you use both via Swift Package Manager. It also fixes a number of warnings people who install Quick via Swift Package Manager on Darwin will receive.

What's Changed

  • Correct a few places where we falsely assume "SWIFT_PACKAGE" == not darwin by @younata in #1223

Full Changelog: v7.0.1...v7.0.2

7.0.1 - re-allow async calls in AsyncSpec's xit

01 Jun 21:42
Compare
Choose a tag to compare

This fixes an oversight where you couldn't use async closures with xit. Thanks @stonko1994 for calling this out!

What's Changed

  • Allow xit in the Async DSL to take in async closures by @younata in #1220

Full Changelog: v7.0.0...v7.0.1

v7.0.0 - AsyncSpec and Human-Readable Test Selectors

20 May 18:18
Compare
Choose a tag to compare

Highlights

Async Test Changes

Quick 7 changes how Async tests are run. Instead of forcing all tests to run in an async context, Quick 7 provides a separate Spec class for Async Tests. Create an AsyncSpec subclass, and all tests inside of that subclass will run in an async context. Tests inside of QuickSpec subclasses will have a similar behavior to what was in Quick 5.

Additionally, Quick 7 changes how the DSL is defined slightly. In Quick 6 and before, the DSL was defined as a series of global functions, available to be called anywhere. In Quick 7, these functions were moved to be static methods on the new SyncDSLUser (which QuickSpec, Behavior, and QuickConfiguration conform to) and AsyncDSLUser (which AsyncSpec and AsyncBehavior conform to) protocols. This allows us to make sure that you are using the correct DSL for the context, and was necessary for this approach.

For example:

class SynchronousSpec: QuickSpec {
    override class func spec() {
        it("runs synchronously, as you'd expect") {
            var ocean: [String] = []
            DispatchQueue.main.async {
                ocean.append("dolphins")
                ocean.append("whales")
            }
            expect(ocean).toEventually(contain("dolphins", "whales"))
        }
    }
}

actor OceanActor<T> {
    var contents: [T] = []
    func append(_ value: T) {
        contents.append(value)
    }
}

class AsynchronousSpec: AsyncSpec {
    override class func spec() {
        it("runs the test in an async context") {
            let ocean = OceanActor<String>()
            Task {
                await ocean.append("dolphins")
                await ocean.append("whales")
            }
            await expect { await ocean.contents }.toEventually(contain("dolphins", "whales"))
        }
    }
}

Unencoded Test Selectors

Furthermore, Quick 7 changes how test selectors are generated for QuickSpec. Now, both AsyncSpec and QuickSpec will use the unencoded test names as the test selectors. Test selectors are now generated by joining the describe/context blocks leading up to the it block with ", ". This makes test names immensely easier to read. For example, with the following spec:

class MySpec: QuickSpec {
    override class func spec() {
        describe("some feature") {
            context("in one case") {
                it("has a behavior") {}
            }

            context("in another case") {
                it("doesn't have the earlier behavior") {}
            }
        }
    }
}

will generate the following test selectors:

  • some feature, in one case, has a behavior
  • some feature, in another case, doesn't have the earlier behavior

You can disable this change by setting the QUICK_USE_ENCODED_TEST_SELECTOR_NAMES environment variable.

Migrating Suggestions

Quick 7 is not a drop-in migration from either Quick 5 or Quick 6. Quick 5 users will have a slightly easier time upgrading, but due to spec being defined as a class method instead of an instance method, there will still be changes.

Doing a Find & Replace of override func spec with override class func spec will take care of the low-hanging fruit. If you have any test helpers that exist as properties or methods of your QuickSpec subclasses, the you will need to either move them inside of the spec function, or outside to another scope. For Objective-C users, this is, for the most part, a drop-in replacement. You will only need to do anything if you do not use the QuickSpecBegin and QuickSpecEnd macros (in which case: do a find & replace of the regex -(\s*)\(void\)(\s*)spec with +$1(void)$2spec).

For migrating from Quick 6 to Quick 7, it would be easiest to also do a Find & Replace of : QuickSpec to : AsyncSpec, then migrate tests that do not need to run in async contexts to be QuickSpecs themselves.

Auto-Generated Changelog

What's Changed

New Contributors

Full Changelog: v6.1.0...v7.0.0