CODEWITHSUNDEEP
swiftunit-testingviper-architecture
Wonton
Wonton

Reputation: 1143

unit testing VIPER protocols

After reading several posts and articles about this issue I'm still confused about how to test a method in a VIPER architecture (for example with Swift).

If I had this code:

Presenter class

protocol InteractorToPresenterProtocol: class {

    func showInfo(info: Info)
}

class Presenter {

    private var interactor: PresenterToInteractorProtocol?

    init() {}

    func makeSomeStuffInPresenter() {

        // make some stuff 
        ...
        interactor?.makeSomeStuffInInteractor()
    }
}

extension Presenter : InteractorToPresenterProtocol {

    func showInfo(info: Info) {

       print(info)
    }    
}

Interactor class:

protocol PresenterToInteractorProtocol: class {

    func makeSomeStuffInInteractor()
}

class Interactor {

    private var presenter: InteractorToPresenterProtocol?

    init() {}
}

extension Interactor : PresenterToInteractorProtocol {

    func makeSomeStuffInInteractor() {

       // make some stuff 
       ...
       presenter?.showInfo(info)
    }    
}

How should I test makeSomeStuffInPresenter method?

Upvotes: 4

Views: 3409

Answers (1)

navroz
navroz

Reputation: 402

You can check the attached sample.

The basic understanding of viper architecture is below.

View: Manages the view displayed to the user. Interactor : Handles the business logic. Presenter: Controls the communication between View and Interactor. Entities : Are the modal classes. Router: Is responsible for managing the Navigation.

Writing the unit test cases.

For Interactor : You can opt Interactor protocol to a mock class and call it's function with positive and negative cases and your Presenter will fulfil the test case expectation.

For Presenter : Similarly, you can mock Interactor, View and call Presenter function and view will fulfil the test case expectation.

In general, for each zone z in {V,I,P,E,R}, you can mock up to the other 4 with simulated simplistic perfection & repeatability so that the zone-under-test (ZUT) is the only zone whose real source code is being exercised (in isolation).

Upvotes: 6

Related Questions