FAQ
Hello

I downloaded this git repo https://github.com/hoisie/mustache

If I run:
go test mustache_test.go
./mustache_test.go:171: undefined: Render
./mustache_test.go:181: undefined: RenderFile
./mustache_test.go:191: undefined: RenderFile
./mustache_test.go:209: undefined: Render
./mustache_test.go:210: undefined: Render
./mustache_test.go:225: undefined: Render
./mustache_test.go:249: undefined: RenderInLayout
FAIL command-line-arguments [build failed]

Why doesn't it work?

If you could describe the workflow that would be great, like say I update
mustache.go, what would I have to do to then run the test?

Do you guys make helper scripts to quicken things up?

--
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Search Discussions

  • Rodrigo Kochenburger at Jan 21, 2014 at 3:04 am
    http://golang.org/doc/code.html

    - RK

    On Mon, Jan 20, 2014 at 7:02 PM, S Ahmed wrote:

    Hello

    I downloaded this git repo https://github.com/hoisie/mustache

    If I run:
    go test mustache_test.go
    ./mustache_test.go:171: undefined: Render
    ./mustache_test.go:181: undefined: RenderFile
    ./mustache_test.go:191: undefined: RenderFile
    ./mustache_test.go:209: undefined: Render
    ./mustache_test.go:210: undefined: Render
    ./mustache_test.go:225: undefined: Render
    ./mustache_test.go:249: undefined: RenderInLayout
    FAIL command-line-arguments [build failed]

    Why doesn't it work?

    If you could describe the workflow that would be great, like say I update
    mustache.go, what would I have to do to then run the test?

    Do you guys make helper scripts to quicken things up?

    --
    You received this message because you are subscribed to the Google Groups
    "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Matt Silverlock at Jan 21, 2014 at 3:24 am
    To give you some guidance:

    - The package needs to be on your GOPATH (use go get
    github.com/hoisie/mustache)
    - You should run `go test` in the package directory or `go test
    github.com/hoisie/mustache` when elsewhere on your GOPATH
    - Read the article Rodrigo linked :)

    On Tuesday, January 21, 2014 11:02:04 AM UTC+8, gitted wrote:

    Hello

    I downloaded this git repo https://github.com/hoisie/mustache

    If I run:
    go test mustache_test.go
    ./mustache_test.go:171: undefined: Render
    ./mustache_test.go:181: undefined: RenderFile
    ./mustache_test.go:191: undefined: RenderFile
    ./mustache_test.go:209: undefined: Render
    ./mustache_test.go:210: undefined: Render
    ./mustache_test.go:225: undefined: Render
    ./mustache_test.go:249: undefined: RenderInLayout
    FAIL command-line-arguments [build failed]

    Why doesn't it work?

    If you could describe the workflow that would be great, like say I update
    mustache.go, what would I have to do to then run the test?

    Do you guys make helper scripts to quicken things up?
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Dave Cheney at Jan 21, 2014 at 4:55 am
    `go test` _always_ takes arguments in the form of packages. You can give
    the package name(s) explicitly, ie

      `go test github.com/hoisie/mustache`,

    implicitly

      `cd $GOPATH/src/github.com/hoisie/mustache && go test .`

    by default, if no arguments are provided go test treats the current
    directory as a package, so in the line above, `go test .` and `go test` are
    identical in function.

    The ability to pass a single file to go build/test/install is a degenerate
    case bought about by go run taking a single file. This should be considered
    an exception to the rule outlined above.

    On Tue, Jan 21, 2014 at 2:24 PM, Matt Silverlock wrote:

    To give you some guidance:

    - The package needs to be on your GOPATH (use go get
    github.com/hoisie/mustache)
    - You should run `go test` in the package directory or `go test
    github.com/hoisie/mustache` <http://github.com/hoisie/mustache> when
    elsewhere on your GOPATH
    - Read the article Rodrigo linked :)

    On Tuesday, January 21, 2014 11:02:04 AM UTC+8, gitted wrote:

    Hello

    I downloaded this git repo https://github.com/hoisie/mustache

    If I run:
    go test mustache_test.go
    ./mustache_test.go:171: undefined: Render
    ./mustache_test.go:181: undefined: RenderFile
    ./mustache_test.go:191: undefined: RenderFile
    ./mustache_test.go:209: undefined: Render
    ./mustache_test.go:210: undefined: Render
    ./mustache_test.go:225: undefined: Render
    ./mustache_test.go:249: undefined: RenderInLayout
    FAIL command-line-arguments [build failed]

    Why doesn't it work?

    If you could describe the workflow that would be great, like say I update
    mustache.go, what would I have to do to then run the test?

    Do you guys make helper scripts to quicken things up?
    --
    You received this message because you are subscribed to the Google Groups
    "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • S Ahmed at Jan 21, 2014 at 3:58 pm
    Thanks Dave (and others).

    What I mean is, if I update the mustache.go file, do I have to build it in
    order for the call to 'go test' to pickup the latest change?

    On Mon, Jan 20, 2014 at 11:55 PM, Dave Cheney wrote:

    `go test` _always_ takes arguments in the form of packages. You can give
    the package name(s) explicitly, ie

    `go test github.com/hoisie/mustache` <http://github.com/hoisie/mustache>
    ,

    implicitly

    `cd $GOPATH/src/github.com/hoisie/mustache && go test .`

    by default, if no arguments are provided go test treats the current
    directory as a package, so in the line above, `go test .` and `go test` are
    identical in function.

    The ability to pass a single file to go build/test/install is a degenerate
    case bought about by go run taking a single file. This should be considered
    an exception to the rule outlined above.

    On Tue, Jan 21, 2014 at 2:24 PM, Matt Silverlock wrote:

    To give you some guidance:

    - The package needs to be on your GOPATH (use go get
    github.com/hoisie/mustache)
    - You should run `go test` in the package directory or `go test
    github.com/hoisie/mustache` <http://github.com/hoisie/mustache> when
    elsewhere on your GOPATH
    - Read the article Rodrigo linked :)

    On Tuesday, January 21, 2014 11:02:04 AM UTC+8, gitted wrote:

    Hello

    I downloaded this git repo https://github.com/hoisie/mustache

    If I run:
    go test mustache_test.go
    ./mustache_test.go:171: undefined: Render
    ./mustache_test.go:181: undefined: RenderFile
    ./mustache_test.go:191: undefined: RenderFile
    ./mustache_test.go:209: undefined: Render
    ./mustache_test.go:210: undefined: Render
    ./mustache_test.go:225: undefined: Render
    ./mustache_test.go:249: undefined: RenderInLayout
    FAIL command-line-arguments [build failed]

    Why doesn't it work?

    If you could describe the workflow that would be great, like say I
    update mustache.go, what would I have to do to then run the test?

    Do you guys make helper scripts to quicken things up?
    --
    You received this message because you are subscribed to the Google Groups
    "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
    --
    You received this message because you are subscribed to the Google Groups
    "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Minux at Jan 21, 2014 at 6:06 pm

    On Jan 21, 2014 10:58 AM, "S Ahmed" wrote:
    What I mean is, if I update the mustache.go file, do I have to build it
    in order for the call to 'go test' to pickup the latest change?
    No. go test will always build the package for test (it's necessary because
    one can put test code in the same package)

    --
    You received this message because you are subscribed to the Google Groups "golang-nuts" group.
    To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupgolang-nuts @
categoriesgo
postedJan 21, '14 at 3:02a
activeJan 21, '14 at 6:06p
posts6
users5
websitegolang.org

People

Translate

site design / logo © 2022 Grokbase