by zzarcon

由zzarcon

使用Kakapo.js進(jìn)行動(dòng)態(tài)模擬 (Dynamic mocking with Kakapo.js)

3 months after the first commit, Kakapo.js reaches the first release and we are proud to announce that now it is ready to use. Let us introduce you Kakapo.

首次提交3個(gè)月后， Kakapo.js到達(dá)了第一個(gè)發(fā)行版，我們很自豪地宣布現(xiàn)在可以使用了。 讓我們向您介紹Kakapo。

Kakapo - The next generation mocking framework in JavascriptKakapo-Java的下一代模擬框架

Kakapo is just a set of tools that tries to make your life easier when building web apps, specially when creating client side mocks. It provides components and APIs which let you easily replicate your backend logic and responses in the client-side.

Kakapo只是一組工具，可在構(gòu)建Web應(yīng)用程序時(shí)使您的生活更加輕松，特別是在創(chuàng)建客戶端模擬時(shí) 。 它提供了組件和API，使您可以輕松地在客戶端復(fù)制后端邏輯和響應(yīng)。

This is nothing new and I’m quite sure you are familiar with tools like jquery-mockjax, FakeXMLHttpRequest or fetch-mock, those tools are great and have been there for quite a loot of time but in my opinion they are just one part of the solution of a big problem.

這并不是什么新鮮事，我敢肯定，您熟悉諸如jquery-mockjax ， FakeXMLHttpRequest或fetch-mock之類的工具，這些工具很棒，并且已經(jīng)存在了很長(zhǎng)一段時(shí)間，但在我看來(lái)，它們只是其中的一部分解決一個(gè)大問(wèn)題。

Why should you care about client side mocking? To solve the Backend-Bottleneck.

您為什么要關(guān)心客戶端嘲笑？ 解決Backend-Bottleneck問(wèn)題 。

后端瓶頸 (Backend Bottleneck)

Last sprint retrospective, after the third sprint in a row missing more than 50% of the planed points, we were starting to ask ourselves what was going wrong. Some back end devs were saying:

上次沖刺回顧，在連續(xù)第三次沖刺錯(cuò)過(guò)了超過(guò)50％的計(jì)劃點(diǎn)之后，我們開(kāi)始問(wèn)自己出了什么問(wèn)題。 一些后端開(kāi)發(fā)人員在說(shuō)：

• Yeah, we thought it was an easy task but we had to spend 1 week refactoring the current functionality to make it working as expected…

  是的，我們認(rèn)為這是一項(xiàng)輕松的任務(wù)，但是我們不得不花1周的時(shí)間來(lái)重構(gòu)當(dāng)前功能，以使其按預(yù)期工作……

• Too much not planned stuff came out and we had to take care of those issues happening in production…

  太多計(jì)劃外的東西出來(lái)了，我們不得不照顧生產(chǎn)中發(fā)生的那些問(wèn)題……

• Staging servers were not working at all and we had to re-deploy the service more than 5 times…

  登臺(tái)服務(wù)器根本無(wú)法正常工作，我們不得不重新部署該服務(wù)超過(guò)5次…

On the other side, front end devs:

另一方面，前端開(kāi)發(fā)人員：

• I spent the whole Monday trying to figure out why the endpoint was returning 500 status code instead of getting the expected response…

  我花了整個(gè)星期一試圖弄清楚為什么端點(diǎn)返回500狀態(tài)代碼而不是得到預(yù)期的響應(yīng)…

• We were building the user profile but the create endpoint was not documented, so we couldn’t make it for the release…

  我們正在構(gòu)建用戶個(gè)人資料，但未記錄創(chuàng)建端點(diǎn)，因此我們無(wú)法在發(fā)布中使用它…

• Yesterday I had to switch too many times within different staging environments that I didn’t had time to work on the feature…

  昨天，我不得不在不同的登臺(tái)環(huán)境中切換太多次，以至于我沒(méi)有時(shí)間來(lái)使用該功能……

I was very frustrated about the current situation and, specially, not being able to ship a small feature in the estimated time. It took me quite some time to realize that it was not a backend or client problem: the issue was something deeper and would require more time and effort to be fixed.

對(duì)于當(dāng)前的情況，我感到非常沮喪，特別是無(wú)法在預(yù)計(jì)的時(shí)間內(nèi)發(fā)布小功能。 我花了相當(dāng)多的時(shí)間才意識(shí)到這不是后端或客戶問(wèn)題：這個(gè)問(wèn)題更深層次，需要花費(fèi)更多時(shí)間和精力來(lái)解決。

What about not dealing with backend issues and staging environments but instead building the feature based on a JSON response agreed with the backend team beforehand?不處理后端問(wèn)題和暫存環(huán)境，而是根據(jù)事先與后端團(tuán)隊(duì)同意的JSON響應(yīng)來(lái)構(gòu)建功能，該怎么辦？

Let’s see a basic example to get an idea of how it works:

讓我們看一個(gè)基本的例子，以了解其工作原理：

In the example above we are just defining a couple of endpoints and one factory, then we define some business logic inside the request handlers in order to return the fake responses. To do this we use three key elements of Kakapo:

在上面的示例中，我們僅定義了兩個(gè)端點(diǎn)和一個(gè)工廠，然后在請(qǐng)求處理程序中定義了一些業(yè)務(wù)邏輯，以便返回假響應(yīng)。 為此，我們使用了Kakapo的三個(gè)關(guān)鍵要素：

• Router: Kakapo’s router recognizes URLs (routes) and dispatches them to the associated handlers. It also provides a request object as argument that gives you useful information about the incoming request.

  路由器 ：Kakapo的路由器識(shí)別URL(路由)，并將其分派到關(guān)聯(lián)的處理程序。 它還提供了一個(gè)請(qǐng)求對(duì)象作為參數(shù)，為您提供有關(guān)傳入請(qǐng)求的有用信息。

• Database: This class along with factories and relationships allows you to define how your entities should be represented and their behaviors.

  數(shù)據(jù)庫(kù) ：該類與工廠和關(guān)系一起使您可以定義應(yīng)如何表示實(shí)體及其行為。

• Server: It connects all other components and lets you activate or deactivate them; this feature gives you the ability to switch between multiple databases and routers, we call this scenarios.

  服務(wù)器 ：它連接所有其他組件，并允許您激活或停用它們； 此功能使您能夠在多個(gè)數(shù)據(jù)庫(kù)和路由器之間切換，我們將其稱為“ 方案” 。

現(xiàn)實(shí)生活中的客戶端嘲笑 (Client side mocking in real life)

Usually mocking APIs is done by creating a static JSON for every single request and testing against it. Creating and maintaining the JSON is a repetitive task and error-prone.

通常，通過(guò)為每個(gè)請(qǐng)求創(chuàng)建靜態(tài)JSON并對(duì)其進(jìn)行測(cè)試來(lái)完成模擬API。 創(chuàng)建和維護(hù)JSON是一項(xiàng)重復(fù)性任務(wù)，容易出錯(cuò)。

Kakapo, instead, lets you dynamically mock your responses by defining how they should look like and automatically serialize them into JSON.

相反，Kakapo允許您通過(guò)定義響應(yīng)的外觀來(lái)動(dòng)態(tài)模擬響應(yīng)，并自動(dòng)將其序列化為JSON。

As an example, let’s try to make a CRUD

例如，讓我們嘗試制作CRUD

That’s how easy is to replicate a CRUD with Kakapo, you might also take a look at fake data and serializers to see some goodies of Kakapo.

用Kakapo復(fù)制CRUD很容易，您還可以查看偽數(shù)據(jù)和序列化程序，以了解Kakapo的一些優(yōu)點(diǎn)。

技術(shù)挑戰(zhàn) (Technical challenges)

Besides all the stuff we have learned in the process of building the library, I would like to point out some of the most challenging things we had to face:

除了我們?cè)跇?gòu)建庫(kù)的過(guò)程中學(xué)到的所有東西之外，我還要指出一些我們必須面對(duì)的最具挑戰(zhàn)性的事情：

攔截器 (Interceptors)

The interceptors components are the ones in charge of intercepting the user request, check if matches any of the routes and apply the mock, they are designed in such a pluggable way that the user can define his owns. Currently we are supporting the browser networking APIs, XMLHttpRequest and fetch but soon we will support Node.js ?.

攔截器的組件是負(fù)責(zé)攔截用戶請(qǐng)求，檢查是否匹配任何路由并應(yīng)用模擬的組件，它們以可插入的方式設(shè)計(jì)，用戶可以定義自己的。 當(dāng)前，我們支持瀏覽器網(wǎng)絡(luò)API， XMLHttpRequest和fetch，但不久之后我們將支持Node.js？。

Reinventing the wheel is not implicitly bad. You can learn a lot doing it.重新發(fā)明輪子并不是很壞。 您可以學(xué)到很多東西。

I found this component complicated because you have to replicate the same functionality that the browser APIs provides, as soon as you behave a bit differently, the application might break since it depends on the native behavior. You can learn a lot while building this stuff directly with native APIs instead of using wrappers like jQuery, because you will really understand how it internally works.

我發(fā)現(xiàn)此組件很復(fù)雜，因?yàn)槟仨殢?fù)制瀏覽器API提供的相同功能，一旦行為有所不同，應(yīng)用程序可能會(huì)中斷，因?yàn)樗Q于本機(jī)行為。 在直接使用本機(jī)API而不是像jQuery這樣的包裝器直接構(gòu)建這些東西時(shí)，您可以學(xué)到很多東西，因?yàn)槟鷮⒄嬲私馑膬?nèi)部工作原理。

While implementing the interceptors we had to make sure to not break popular networking libraries like jQuery and Superagent; we created integration tests to ensure that Kakapo will continue to work as expected after introducing new changes.

在實(shí)現(xiàn)攔截器時(shí)，我們必須確保不要破壞流行的聯(lián)網(wǎng)庫(kù)，例如jQuery和Superagent ； 我們創(chuàng)建了集成測(cè)試 以確保Kakapo在進(jìn)行新更改后將繼續(xù)按預(yù)期工作。

測(cè)試中 (Testing)

Testing is a must when developing software, but is even more critical in open source projects that other developers will potentially use. We always had this in mind while creating Kakapo and this was the first project I ever did in a strict TDD way. I have to admit that the feeling I had at the beginning was way different than the one I have now. Sometimes I felt that writing so many tests was slowing us down, but now with high code coverage, I feel really confident when I have to refactor a critical component or add a new feature to the library.

在開(kāi)發(fā)軟件時(shí)，測(cè)試是必須的，但在其他開(kāi)發(fā)人員可能使用的開(kāi)源項(xiàng)目中，測(cè)試則更為關(guān)鍵。 在創(chuàng)建Kakapo時(shí)，我們始終牢記這一點(diǎn)，這是我有史以來(lái)以嚴(yán)格的TDD方式進(jìn)行的第一個(gè)項(xiàng)目。 我必須承認(rèn)，我一開(kāi)始的感覺(jué)與我現(xiàn)在的感覺(jué)有很大不同。 有時(shí)，我覺(jué)得編寫這么多的測(cè)試會(huì)拖慢我們的腳步，但是現(xiàn)在有了高代碼覆蓋率 ，當(dāng)我必須重構(gòu)關(guān)鍵組件或向庫(kù)中添加新功能時(shí)，我感到非常有信心。

This is something you have to introduce in your workflow incrementally and define with the team. Since this was the biggest open source project I ever worked on, I learned how to coordinate and work with a team. Sometimes things need to be discussed twice or more just to make sure that all the members are on the same page, but at the end is going to work out.

您必須在工作流程中逐步引入并與團(tuán)隊(duì)一起定義。 由于這是我從事過(guò)的最大的開(kāi)源項(xiàng)目，因此我學(xué)會(huì)了如何與團(tuán)隊(duì)協(xié)調(diào)和合作。 有時(shí)需要討論兩次或更多次 ，以確保所有成員都在同一頁(yè)面上，但最后要進(jìn)行工作。

文件的重要性 (Importance of documentation)

Developers hate writing documentation. Unfortunately, it is as important as having a good library and will be the first thing your users and contributors will see.

開(kāi)發(fā)人員討厭編寫文檔。 不幸的是，它與擁有一個(gè)好的庫(kù)同樣重要，并且將是您的用戶和貢獻(xiàn)者首先看到的。

Think about it this way: you have been building your library for some months and now is finally ready, don’t you think it is worth the effort to spend some days building a website and writing some good examples?

這樣考慮：您已經(jīng)建立了幾個(gè)月的圖書(shū)館，現(xiàn)在終于可以使用了，您認(rèn)為花幾天時(shí)間建立一個(gè)網(wǎng)站并編寫一些好的示例值得您付出嗎？

This is a talk from React Europe 2016 in which Christopher Chedeau explains how Facebook deal with spreading open source libraries.

這是來(lái)自React Europe 2016的一個(gè)演講， 克里斯托弗·切多( Christopher Chedeau)在演講中解釋了Facebook如何處理傳播的開(kāi)源庫(kù)。

杰基爾 (Jekyll)

Jekyll literally saved us, it improved the way we write documentation and the velocity. Before choosing Jekyll, I used to build static websites with some css and html to then place there the docs. However, some developers might not be fluent and miss the simplicity of Markdown. That’s why we decided to go for Jekyll which lets you write your pages in Kramdown (markdown with steroids) and is integrated with Github Pages.

Jekyll從字面上拯救了我們，它改善了我們編寫文檔的方式和速度。 在選擇Jekyll之前，我曾經(jīng)用一些CSS和html構(gòu)建靜態(tài)網(wǎng)站，然后將文檔放置在那里。 但是，有些開(kāi)發(fā)人員可能不會(huì)流利，會(huì)錯(cuò)過(guò)Markdown的簡(jiǎn)單性。 這就是為什么我們決定選擇Jekyll的原因，它可以讓您用Kramdown編寫頁(yè)面(類固醇的降價(jià))，并與Github Pages集成。

Once we felt comfortable with the status of the docs and the examples, we also wanted to give a good first impression to newcomers. We created a script which fetches the md file from the github page, adds some content and outputs the readme ?

一旦我們對(duì)文檔和示例的狀態(tài)感到滿意，我們還希望給新手一個(gè)良好的第一印象。 我們創(chuàng)建了一個(gè)腳本 ，該腳本從github頁(yè)面獲取md文件 ，添加了一些內(nèi)容并輸出了自述文件 ？

演示應(yīng)用 (Demo Apps)

Everyone likes demos, they show what your library does and how it does it. It might sound weird, but it will also help you to learn how to use your own library, as well as finding bugs or missing features.

每個(gè)人都喜歡演示，他們演示了您的庫(kù)做什么以及如何做。 聽(tīng)起來(lái)可能很奇怪，但是它也將幫助您學(xué)習(xí)如何使用自己的庫(kù)，以及發(fā)現(xiàn)錯(cuò)誤或缺少功能。

Until we built our first todo app using Kakapo we didn’t realize about the major pain points and how to solve them, that’s why we later built our second demo app, a github explorer.

直到我們使用Kakapo構(gòu)建了第一個(gè)todo應(yīng)用程序之前，我們才意識(shí)到主要的難點(diǎn)以及如何解決它們，這就是為什么我們后來(lái)構(gòu)建了第二個(gè)演示應(yīng)用程序(一個(gè)github Explorer)的原因 。

Having a good library without documentation is like having rocket that nobody knows how to use it.擁有一個(gè)沒(méi)有文檔的好的圖書(shū)館就像擁有一個(gè)沒(méi)人知道如何使用它的火箭一樣。

路線圖 (ROADMAP)

The project just started but we have ambitious plans for it; feel free to check the open issues or open new ones, we will really appreciate it! Here are some of the most important:

這個(gè)項(xiàng)目剛剛開(kāi)始，但是我們有雄心勃勃的計(jì)劃。 隨時(shí)檢查未解決的問(wèn)題或發(fā)現(xiàn)新的問(wèn)題，我們將非常感謝！ 以下是一些最重要的信息：

• Full JSON API serializer support

  全面的JSON API序列化程序支持

• Node.js interceptors support

  Node.js攔截器支持

• Async handlers support

  異步處理程序支持

We are also working hard to finish the Swift version of Kakapo which is almost ready for the beta phase and we think is going to be a game changer to build iOS applications: stay tuned! ?

我們也正在努力完成Kakapo的Swift版本，該版本幾乎已經(jīng)可以進(jìn)入Beta測(cè)試階段，我們認(rèn)為它將成為構(gòu)建iOS應(yīng)用程序的顛覆者：敬請(qǐng)期待！ ？

翻譯自: https://www.freecodecamp.org/news/dynamic-mocking-with-kakapo-js-bdbd3d7b58e2/

總結(jié)

以上是生活随笔為你收集整理的使用Kakapo.js进行动态模拟的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問(wèn)題。

如果覺(jué)得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。