douhuan3448 2015-12-25 11:13
浏览 29
已采纳

如何处理“ fmt” golang库软件包进行CLI测试

Disclaimer: I wish you a merry XMas and I hope my question does not disturb you!

sample.go:

package main

import(
    "fmt"
    "os"
)


type sample struct {
    value int64
}

func (s sample) useful() {
    if s.value == 0 {
        fmt.Println("Error: something is wrong!")
        os.Exit(1)
    } else {
        fmt.Println("May the force be with you!")
    }
}

func main() {
    s := sample{42}
    s.useful()

    s.value = 0
    s.useful()
}

// output:
// May the force be with you!
// Error: something is wrong!
// exit status 1

I did a lot of research on how to use interfaces in golang testing. But so far I was not able to wrap my head around this completely. At least I can not see how interfaces help me when I need to "mock" (apologies for using this word) golang std. library packages like "fmt".

I came up with two scenarios:

  1. use os/exec to test the command line interface
  2. wrap fmt package so I have control and am able to check the output strings

I do not like both scenarios:

  1. I experience going through the actual command line a convoluted and not-performant (see below). Might have portability issues, too.
  2. I believe this is the way to go but I fear that wrapping the fmt package might be a lot of work (at least wrapping the time package for testing turned out a non-trivial task (https://github.com/finklabs/ttime)).

Actual Question here: Is there another (better/simpler/idiomatic) way? Note: I want to do this in pure golang, I am not interested in the next testing framework.

cli_test.go:

package main

import(
    "os/exec"
    "testing"
)


func TestCli(t *testing.T) {
    out, err := exec.Command("go run sample.go").Output()
    if err != nil {
        t.Fatal(err)
    }
    if string(out) != "May the force be with you!
Error: this is broken and not useful!
exit status 1" {
        t.Fatal("There is something wrong with the CLI")
    }
}
  • 写回答

2条回答 默认 最新

  • duanjingsen7904 2015-12-25 13:56
    关注

    Chapter 11 of Kerningham's Book gives a good solution to this question. The trick is to change the calls to fmt.Printline() to calls to fmt.Fprint(out, ...) where out is initialised to os.Stdout

    This can be overwritten in the test harness to new(bytes.Buffer) allowing the test to capture the output.

    See https://github.com/adonovan/gopl.io/blob/master/ch11/echo/echo.go and https://github.com/adonovan/gopl.io/blob/master/ch11/echo/echo_test.go

    edited by OP... sample.go:

    package main
    
    
    import(
        "fmt"
        "os"
        "io"
    )
    
    
    var out io.Writer = os.Stdout // modified during testing
    var exit func(code int) = os.Exit
    
    type sample struct {
        value int64
    }
    
    
    func (s sample) useful() {
        if s.value == 0 {
            fmt.Fprint(out, "Error: something is wrong!
    ")
            exit(1)
        } else {
            fmt.Fprint(out, "May the force be with you!
    ")
        }
    }
    
    
    func main() {
        s := sample{42}
        s.useful()
    
        s.value = 0
        s.useful()
    }
    
    // output:
    // May the force be with you!
    // Error: this is broken and not useful!
    // exit status 1
    

    cli_test.go:

    package main
    
    import(
        "bytes"
        "testing"
    )
    
    
    func TestUsefulPositive(t *testing.T) {
        bak := out
        out = new(bytes.Buffer)
        defer func() { out = bak }()
    
        s := sample{42}
        s.useful()
        if out.(*bytes.Buffer).String() != "May the force be with you!
    " {
            t.Fatal("There is something wrong with the CLI")
        }
    
    }
    
    
    func TestUsefulNegative(t *testing.T) {
        bak := out
        out = new(bytes.Buffer)
        defer func() { out = bak }()
        code := 0
        osexit := exit
        exit = func(c int) { code = c }
        defer func() { exit = osexit }()
    
        s := sample{0}
        s.useful()
        if out.(*bytes.Buffer).String() != "Error: something is wrong!
    " {
            t.Fatal("There is something wrong with the CLI")
        }
        if code != 1 {
            t.Fatal("Wrong exit code!")
        }
    }
    
    本回答被题主选为最佳回答 , 对您是否有帮助呢?
    评论
查看更多回答(1条)

报告相同问题?

悬赏问题

  • ¥15 linux驱动,linux应用,多线程
  • ¥20 我要一个分身加定位两个功能的安卓app
  • ¥15 基于FOC驱动器,如何实现卡丁车下坡无阻力的遛坡的效果
  • ¥15 IAR程序莫名变量多重定义
  • ¥15 (标签-UDP|关键词-client)
  • ¥15 关于库卡officelite无法与虚拟机通讯的问题
  • ¥15 目标检测项目无法读取视频
  • ¥15 GEO datasets中基因芯片数据仅仅提供了normalized signal如何进行差异分析
  • ¥100 求采集电商背景音乐的方法
  • ¥15 数学建模竞赛求指导帮助