Cannot make Goose DB Migration working for Go testing

I am currently learning Golang for web programming and now I continue by learning about database,Rest API and testing in Golang.

and now I got an issue with Goose database Migration and Go Testing integration.

I want to integrate goose migration to my Go testing code, my scenario is to up all migrations before test and then reset all database once testing is done.

my problem is I can't find any documentation/sample code to do it with Goose.

I also have tried to execute the goose command using exec.Command() but it always returns exit status 1

this is my existing code to trigger the migration up before testing being executed:

func pretest() {
      var args = []string{
          os.Getenv("DB_SERVER"),
          "\"user=" + os.Getenv("DB_USERNAME") + " dbname=" + os.Getenv("DB_TEST_NAME") + " sslmode=disable\"",
          "up",
      }   
  
      exe := exec.Command("goose", args...)
      exe.Dir = os.Getenv("DB_MIGRATION")
      /* result, err := exe.Output()*/
      //fmt.Println(string(result))
      /*fmt.Println(err)*/
  
      output := exe.Run()
      fmt.Println(output)
  }

$ go test -v
exit status 1
testing: warning: no tests to run
PASS
ok

my question is it possible to trigger migration (up/down/reset) from inside Go Code (in this case is testing code) ?

Why exec.Command() keep returning code status 1 but it work well when I execute another linux command (ls, pwd, mkdir are work well in the same way) ?

I am new to go as well, so my analysis may be totally wrong but since goose seems to be an open source package itself, I took a look at the cmd/goose/main.go file that refers to how the commands are called internally:

if err := goose.Run(command, db, *dir, arguments...); err != nil {
	log.Fatalf("goose run: %v", err)
}

Which calls the Runfunc that is defined in the goose.go

func Run(command string, db *sql.DB, dir string, args ...string) error {

That takes argument command string argument with db strings as well.

But if you would like to still work with the execCommand then maybe you could take a look at goose_test.go file which which passes arguments dir where the migrations are to be run perhaps.

Finally I got this issue solved by changing this following line on my code:

"\"user=" + os.Getenv("DB_USERNAME") + " dbname=" + os.Getenv("DB_TEST_NAME") + " sslmode=disable\"",

to:

"user=" + os.Getenv("DB_USERNAME") + " dbname=" + os.Getenv("DB_TEST_NAME") + " sslmode=disable",