前后端分离使用 mest 做契约测试跟踪 API 接口变更
Open
- Dominant language
- No language data
- Stars
- 26
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
## 前后端分离：使用 mest 做契约测试跟踪 API 接口变更
还在担心后端 API 变更对前端的影响？快来使用 mest 在实施前后端分离架构的过程中，最让人苦恼的莫过于： API 发生了变化 。API 发生变化的原因那可是相当的丰富：业务变化、字段名出错、第三方接口不匹配等等，但是这些都不重要——一个字段从 string 变成了…
April 24, 2018 at 09:59PM
via Instapaper http://zhuanlan.zhihu.com/p/36030249
Contributor guide
No contributing guide indexed for this repository
Research direction
Read the linked article at http://zhuanlan.zhihu.com/p/36030249 and the issue title for context about using mest for contract testing during frontend/backend separation. The payload names no repository files, tests, entry points, or concrete change, so the intended implementation and completion criteria remain undefined.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100