Stubs, Mocks, and Spies

stubs:

create fake object, and assume this fake object can response what information, response, make sure the main tested object can get the consistent result

mocks

same with stubs, but must be executed

https://github.com/festime/stubs-mocks-spies-in-rspec

 from https://danielzhangqinglong.github.io/2015/04/07/rspec-mock/

比如說, 現在要去測試一下Twitter是不是成功發了一條推文:

1 2 3 4 5 6 7 8 9 10

require 'twitter' class TwitterEmotion def tweet twitter_client.update "I am very happy" end def twitter_client Twitter::REST::Client .new end end

測試代碼:

1 2 3 4

it "should tweet successfully" do emotion = TwitterEmotion. new expect{ emotion.tweet }.not_to raise_error end

但是這真的會把你的推文發生出去,還有,如果網絡環境不好或者Twitter的服務器沒有及時處理請求,那麼我這邊的測試就會跑不通,等等問題. 
正因為如此,才需要把使用Twitter服務的部分用mock代替.這樣測試就不會和Twitter進行交互了.下面是使用mock後的測試:

1 2 3 4 5 6 7 8 9 10 11 12

it "should tweet successfully" do # mock Twitter client twitter_client_mock = double( 'Twitter client' ) # 讓update方法可以在mock對像上調用 allow(twitter_client_mock). to receive(:update) emotion = TwitterEmotion. new allow(emotion). to receive(:twitter_client).and_return(twitter_client_mock) # 如果在emotion上調用了twitter_client, 那麼就返回twitter_client_mock expect{ emotion.tweet }.not_to raise_error end

allow (想要替換方法的對象) . to receive (所要替換的方法) . and_return (返回值對象)


allow (mock對象) . to receive (方法) . and_raise (異常)

Initialize the serializer

ActiveModel::ArraySerializer.new(Funding.all, each_serializer: FundingSerializer).to_json

http://stackoverflow.com/questions/17542793/how-do-you-initialize-an-activemodelserializer-class-with-an-activerecordrel

For me I passed the view_context to the array serializer:
ActiveModel::ArraySerializer.new(your_array, each_serializer: YourSerializer, scope: self.view_context)

how to pass scope

https://github.com/rails-api/active_model_serializers/issues/510

好的架構源於不停地衍變

架構的演進


http://www.csdn.net/article/2015-10-24/2826028

所有東西在一台機器上








資料庫變成瓶頸
改成分佈式架構



將業務層 資料庫層 在做垂直的拆分 減輕壓力




多一個服務層 來較用呼叫其他方法

Why I No Longer Use MVC Frameworks

http://www.infoq.com/articles/no-more-mvc-frameworks

 In traditional MVC, the action (controller) would call an update method on the model and upon success (or error) decide how to update the view

The SAM pattern can be represented by the following expression:

         V = S( vm( M.present( A(data) ) ), nap(M))

which stipulates that the view V of a system can be computed, after an action A has been applied, as a pure function of the model.

In SAM, A (actions), vm (view-model), nap (next-action predicate) and S (state representation) are and must all be pure functions. With SAM, what we commonly call the “state” (the values of the properties of the system) is entirely confined to the model and the logic that changes these values is not visible outside the model itself. 

The SAM pattern changes completely the paradigm of front-end architectures because, on the foundation of TLA+, the business logic can be clearly delineated into:

• Actions as pure functions
• CRUD operations in the model
• States which control automatic Actions