Giter Club home page Giter Club logo

Comments (2)

alexdmotoc avatar alexdmotoc commented on June 9, 2024

Also, it seems there is no way to test for memory leaks. The following example shows a memory leak and a test against it that is passing (it should fail). What is the correct approach for testing against memory leaks?

class MyService {
    var completion: (() -> Void)?

    func perform(completion: @escaping () -> Void) {
        self.completion = completion
        DispatchQueue.main.asyncAfter(deadline: .now() + 0.1, execute: completion)
    }
}

class MyObject {
    var didPerform = false
    let service = MyService()

    func perform(completion: @escaping () -> Void) {
        service.perform {
            self.didPerform = true
            completion()
        }
    }
}

final class MockTest: QuickSpec {
    override func spec() {
        describe("mock test") {
            var sut: MyObject!

            beforeEach {
                sut = MyObject()
            }

            afterEach { [weak sut] in
                expect(sut).to(beNil())
            }

            it("performs") {
                sut.perform {}
                expect(sut.didPerform).toEventually(beTrue())
            }
        }
    }
}

from quick.

brandtdaniels avatar brandtdaniels commented on June 9, 2024

context and describe are the same code implementation, just different meanings in the bdd world. Typically describe is used to describe your subject under test, while the context is used to describe your scenario for either interaction or state testing. The it block is only meant to contain a single test.

For example

describe("Some widget factory") {

  var subject: WidgetFactoryProtocol!
  var mockNetwork: NetworkProtocol!

  beforeEach {
     mockNetwork = MockNetwork()
      subject = WidgetFactoryImpl(network: mockNetwork)
   }

    context("when the network request fails") {
        beforeEach {
            // Setup your scenario described in the context
           mockNetwork.shouldSucceed = false
        }
        it("should fail to produce a widget")  {
            subject.produceWidget()
            expect(subject.didProduceWidget).to(beFalse())
       }
    }

  context("when the network request succeeds") {
      beforeEach {
         // Setup your scenario described in the context
         mockNetwork.shouldSucceed = true
      }
      ........
  }
}

same with afterEach as it's meant to reset things after your specific scenario if you're not reinitializing your subject within each context.

from quick.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.