内容简介:Unit Test -> Integrate Test -> Dev, from fake to realRun unit test by hand or script with go test.Write Unit Test Withfx support to inject some mock component, example:
基本过程
- coding in local IDE,write unit test,
- add & run integrate test(tradeoff between自动化与手动,如果自动化写的少,多动手)
- deploy to dev environment
- deploy to qa or production environment. not be discussed on this page
Requirement
Environment in logic
- IDE environment for develop effectively. Should support debug interactively with ide breakpoint.
- Integrate Test environment. For run integrate by hand or automatically.
- Local Environment.
-
Dev environment.
And QA environment、Prod environment not maintained by dev
Environment in implement
Realness
Unit Test -> Integrate Test -> Dev, from fake to real
Implement
Run unit test by hand or script with go test.
Unit Test
Write Unit Test Withfx support to inject some mock component, example:
func TestFxPopluate(t *testing.T) {
// Some external module that provides a user name.
type Username string
UserModule := fx.Provide(func() Username { return "john" })
var user Username
app := fxtest.New(
t,
UserModule,
fx.Populate(&user),
)
app.RequireStart().RequireStop()
t.Log(user)
}
Integrate Test
use httptest library, example
func TestHttpTestApi(t *testing.T) {
InitTest()
var r *gin.Engine
app := fxtest.New(t, logger.Module, database.Module, cache.Module, config.Module,
dao.Module, handler.ModuleWithDep, router.Module, fx.Populate(&r))
app.RequireStart().RequireStop()
// create request
req, err := http.NewRequest("GET", "/api/v3/test/ping", nil)
if err != nil {
t.Fatal(err)
}
// response checker
rr := httptest.NewRecorder()
r.ServeHTTP(rr, req)
if status := rr.Code; status != http.StatusForbidden {
t.Errorf("handler returned wrong status code: got %v want %v",
status, http.StatusOK)
}
return
/*
expected := `{"message": "pong"}`
if rr.Body.String() != expected {
t.Errorf("handler returned unexpected body: got %v want %v",
rr.Body.String(), expected)
}
*/
}
Distinguish env by shell env value or cmd flag or both, supported by config library
IDE env、Integrate Test env、Local env can use same config、same environment, but with some difference, so use different flag. Different Requirement
- IDE env require run in IDE, so more mock component. Actually one of server、fe run separately in IDE,other run in docker
- Integrate Test should clean db and other state before every run. Integrate can be run in any one of IDE、local、dev、QA env with clean db、state
- Local env require keep state.
Use docker to implement this.
Env define: ["ide", "local", "dev"], and ["qa", "prod"]
Use shell env、cmd flags to determine which env to run, as to load different config and component.
monkey patch
https://github.com/bouk/monkey
可以极大地简化使用依赖注入时的mock替换,避免在更深的层次进行替换时的繁琐操作。
以上所述就是小编给大家介绍的《golang best practice 之 dev测试》,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对 码农网 的支持!
猜你喜欢:- Flutter 学习之路 - 测试(单元测试,Widget 测试,集成测试)
- itest(爱测试)接口测试&敏捷测试管理 7.7.7 发布,接口测试重大升级
- 性能测试vs压力测试vs负载测试
- SpringBoot | 第十三章:测试相关(单元测试、性能测试)
- 敏捷测试VS传统测试对比,6招玩转敏捷测试!
- itest(爱测试)接口测试&敏捷测试管理平台 8.1.0 发布
本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
计算机程序设计艺术(第1卷)
[美] Donald E. Knuth / 清华大学出版社 / 2002-9 / 80.00元
第1卷首先介绍编程的基本概念和技术,然后详细讲解信息结构方面的内容,包括信息在计算机内部的表示方法、数据元素之间的结构关系,以及有效的信息处理方法。此外,书中还描述了编程在模拟、数值方法、符号计算、软件与系统设计等方面的初级应用。此第3版增加了数十项简单但重要的算法和技术,并根据当前研究发展趋势在数学预备知识方面做了大量修改。一起来看看 《计算机程序设计艺术(第1卷)》 这本书的介绍吧!