Measures for Growth with Firebase Remote Config & Unit Testing Using RxSwift
•
0 j'aime•369 vues
The document discusses using Firebase Remote Config and unit testing with RxSwift. It provides an overview of Firebase Remote Config and how it can be used to store feature flags and master data when backend development is not ready. It also discusses writing unit tests with Quick, Nimble, and SwiftyMocky to mock dependencies and generate test cases that cover A/B testing logic and various scenarios. The document emphasizes the importance of understanding context before implementation, utilizing Firebase Remote Config features, and clarifying what to test to avoid overcomplicating specifications and logic.
Recommandé
Contenu connexe
Similaire à Measures for Growth with Firebase Remote Config & Unit Testing Using RxSwift
Similaire à Measures for Growth with Firebase Remote Config & Unit Testing Using RxSwift (20)
Plus de Fumiya Sakai
Plus de Fumiya Sakai (20)
Dernier
Dernier (20)
Measures for Growth with Firebase Remote Config & Unit Testing Using RxSwift
- 5. Growth Hack Process Actively involve people outside your team when thinking about measures. Create ideas & Check the difficulty： Examples of opportunities for active discussion： 🌟 Idea Session Outside Team Inside Team 😄 PdM / EM / Designer / Engineer (iOS / Android) Expert knowledge and opinions： 😄 Data Science / Other Team Member / QA etc.. 🌟 MTG For Growth 🌟 Planning & Refinement
- 9. Architecture overview and connection with Remote Config Create logic via Client that utilizes Firebase Remote Config Presentation Business Logic Domain Logic Infrastructure - DomainModel (Entity) - Repository - DomainService - RestAPI Client - GraphQL Client - UserDefault / Realm - View (ViewController) - Presenter - Contract Connect RxSwift Operator (Single / Maybe / Completable) FirebaseRemoteConfigClient // sourcery: AutoMockable protocol FirebaseRemoteConfigClient { func getFeaturedRecipes() -> Single<[FeaturedRecipeEntityJson]> func getFeaturedRecipeEnabled() -> Single<Bool> func getTrendKeywords() -> Single<[TrendKeywordEntityJson]> func getTrendKeywordEnabled() -> Single<Bool> … (get display data and feature flags) … } UseCase // sourcery: AutoMockable protocol CheckTrendKeywordEnabledUseCase { func execute() -> Single<Bool> } // sourcery: AutoMockable protocol GetTrendKeywordUseCase { func execute() -> Single<[TrendKeyword]> } ① Feature flags. ② Master data. - return Single<Bool> - Fetch from Remote Config - Convert to DomainModel
- 11. A / B Testing in the Presentation layer Example First, A / B Testing is sorted, and then the display process is executed. Presentation checkTrendKeywordEnabledUseCase.execute() .observe(on: mainScheduler) .subscribe( onSuccess: { [weak self] checkTrendKeywordEnabled in guard let weakSelf = self else { return } weakSelf.fetchTrendKeywords( checkTrendKeywordEnabled: checkTrendKeywordEnabled ) }, onFailure: { [weak self] _ in weakSelf.fetchTrendKeywords( checkTrendKeywordEnabled: false ) } ) .disposed(by: disposeBag) private func fetchTrendKeywords(checkTrendKeywordEnabled: Bool) { getTrendKeywordUseCase.execute() .observe(on: mainScheduler) .subscribe( onSuccess: { [weak self] trendKeywords in guard let weakSelf = self else { return } let souldShow = trendKeywords.isEmpty || !checkTrendKeywordEnabled weakSelf.view?.setup(trendKeywords: souldShow ? trendKeywords : []) }, onFailure: { [weak self] _ in guard let weakSelf = self else { return } weakSelf.view?.showError(error: error, closeHandler: {}) } ) .disposed(by: disposeBag) } ① A/B Testing flags ② Master Data
- 12. A point that seems to be good to be careful a little Points to note when implementing A / B testing logic with RxSwift Question (1)： Should Use Bool or Single<Bool> ? 😔 If A/B Testing logic uses Single<Bool>, presentation logic tends to be complicated. Question (2)： A/B Testing logic should integrate Single.zip ? public static func zip<E1, E2, E3, E4, E5, E6, E7, E8>(_ source1: PrimitiveSequence<Trait, E1>, _ source2: PrimitiveSequence<Trait, E2>, _ source3: PrimitiveSequence<Trait, E3>, _ source4: PrimitiveSequence<Trait, E4>, _ source5: PrimitiveSequence<Trait, E5>, _ source6: PrimitiveSequence<Trait, E6>, _ source7: PrimitiveSequence<Trait, E7>, _ source8: PrimitiveSequence<Trait, E8>, resultSelector: @escaping (E1, E2, E3, E4, E5, E6, E7, E8) throws -> Element) -> PrimitiveSequence<Trait, Element> { return PrimitiveSequence(raw: Observable.zip( source1.asObservable(), source2.asObservable(), source3.asObservable(), source4.asObservable(), source5.asObservable(), source6.asObservable(), source7.asObservable(), source8.asObservable(), resultSelector: resultSelector) ) } 😓 The upper limit that can be set with Single.zip is 8. ※ Internal definition of Single.zip
- 13. Unit Testing with Quick + Nimble + SwiftyMocky Grenerate Mock for Unit test library Intro of SwiftyMocky // Install SwiftyMocky CLI $ brew install mint $ mint install MakeAWishFoundation/SwiftyMocky 👉 Swift Package Manager 👉 Test Target // MEMO: Mock preparation required for testing let checkTrendKeywordEnabledUseCase = CheckTrendKeywordEnabledUseCaseMock() let getTrendKeywordUseCase = GetTrendKeywordUseCaseMock() // MEMO: Apply Mock to the class under test let target = TrendKeywordPresenterImpl( checkTrendKeywordEnabledUseCase: checkTrendKeywordEnabledUseCase, getTrendKeywordUseCase: getTrendKeywordUseCase ) // sourcery: AutoMockable protocol CheckTrendKeywordEnabledUseCase { func execute() -> Single<Bool> } // sourcery: AutoMockable protocol GetTrendKeywordUseCase { func execute() -> Single<[TrendKeyword]> } // Generate Mock $ swiftymocky generate Prepare for Unit test SwiftyMocky： https://github.com/MakeAWishFoundation/SwiftyMocky
- 14. Write carefully with various cases added Ensuring behavior that includes A / B test logic as much as possible Test Case Example Test Pattern Strategy describe("#execute") { context(“A/B Testing Target & Get Trend Keywords Success.”) { let checkTrendKeywordEnabled = true let trendkeywords = … (Test Data Example) … beforeEach { checkTrendKeywordEnabledUseCase.given( .execute(willReturn: Single.just(checkTrendKeywordEnabled)) ) getTrendKeywordUseCase.given( .execute(willReturn: Single.just(trendkeywords)) ) } it(“Return Trend Keywords”) { expect(try! target.fetch().toBlocking().first()) .to(equal(trendkeywords)) } } } ① Write Test Quick & Nimble ② Assign Mock & Stub - A/B Testing Logic → return true - Business Logic pattern A → return Single<P> - Common Business Logic → return Single<Q> Expected Result → return R Pattern Case A： - A/B Testing Logic → return false - Business Logic pattern A → return Single<S> - Common Business Logic → return Single<Q> Expected Result → return T Pattern Case B： Secure with Unit Test as much as possible