mirror of
https://github.com/maybe-finance/maybe.git
synced 2025-07-24 15:49:39 +02:00
03a146222d
Breaks our Plaid sync process out into more manageable classes. Notably, this moves the sync process to a distinct, 2-step flow: 1. Import stage - we first make API calls and import Plaid data to "mirror" tables 2. Processing stage - read the raw data, apply business rules, build internal domain models and sync balances This provides several benefits: - Plaid syncs can now be "replayed" without fetching API data again - Mirror tables provide better audit and debugging capabilities - Eliminates the "all or nothing" sync behavior that is currently in place, which is brittle
27 lines
771 B
Ruby
27 lines
771 B
Ruby
require "test_helper"
|
|
|
|
class PlaidItemTest < ActiveSupport::TestCase
|
|
include SyncableInterfaceTest
|
|
|
|
setup do
|
|
@plaid_item = @syncable = plaid_items(:one)
|
|
@plaid_provider = mock
|
|
Provider::Registry.stubs(:plaid_provider_for_region).returns(@plaid_provider)
|
|
end
|
|
|
|
test "removes plaid item when destroyed" do
|
|
@plaid_provider.expects(:remove_item).with(@plaid_item.access_token).once
|
|
|
|
assert_difference "PlaidItem.count", -1 do
|
|
@plaid_item.destroy
|
|
end
|
|
end
|
|
|
|
test "if plaid item not found, silently continues with deletion" do
|
|
@plaid_provider.expects(:remove_item).with(@plaid_item.access_token).raises(Plaid::ApiError.new("Item not found"))
|
|
|
|
assert_difference "PlaidItem.count", -1 do
|
|
@plaid_item.destroy
|
|
end
|
|
end
|
|
end
|