code review 14566048: go.blog/cover: new article about test coverage

go.blog/cover: new article about test coverage

[r, 2013-10-10 22:03:13]

Hello adg,

I'd like you to review this change to
https://code.google.com/p/go.blog

[adg, 2013-10-12 08:01:27]

Looks good

https://codereview.appspot.com/14566048/diff/5001/content/cover.article
File content/cover.article (right):

https://codereview.appspot.com/14566048/diff/5001/content/cover.article#newco...
content/cover.article:30: Go is not a simple language, but the design aims to be
free of special cases that
"simple" is a relative term.
It's certainly simple compared to C++, but not Lisp. Reword? Maybe:
        "Go has a regular syntax that is easy to parse; its design aims to be
        free of special cases that require complex machinery to analyze."

https://codereview.appspot.com/14566048/diff/5001/content/cover.article#newco...
content/cover.article:48: Gofix let us make fundamental changes to the language
and libraries in the run-up to Go 1.0,
link to "Path to Go 1" talk (blog.golang.org/the-path-to-go-1)

https://codereview.appspot.com/14566048/diff/5001/content/cover.article#newco...
content/cover.article:63: The program that provides test coverage in Go 1.2 is
the latest to exploit the tooling support in the Go ecosystem.
I'd swap this and the next paragraph

https://codereview.appspot.com/14566048/diff/5001/content/cover.article#newco...
content/cover.article:90: For the new test coverage tool for Go, we took a
completely different and completely approach that avoids dynamic debugging.
s/and completely //

https://codereview.appspot.com/14566048/diff/5001/content/cover.article#newco...
content/cover.article:94: Here's what happens. Say we have a simple, one-file
package like this:
"Here's an example." ?

https://codereview.appspot.com/14566048/diff/5001/content/cover.article#newco...
content/cover.article:192: Let's try counting statement execution for a standard
package, the <fmt>code</fmt> formatting package.
`fmt` :-)

[r, 2013-10-14 18:12:22]

All addressed and new version uploaded. It can probably sit until we're
ready to launch it.

[adg, 2013-12-02 05:20:30]

Ready to go with this, this week?

https://codereview.appspot.com/14566048/diff/51002/content/cover.article
File content/cover.article (right):

https://codereview.appspot.com/14566048/diff/51002/content/cover.article#newc...
content/cover.article:2: 14 Nov 2013
Let's make this "2 Dec 2013" or "3 Dec 2013"

[r, 2013-12-02 06:28:00]

it's ready. feel free to submit when you want it to land.


On Sun, Dec 1, 2013 at 9:20 PM,  <adg@golang.org> wrote:
> Ready to go with this, this week?
>
>
> https://codereview.appspot.com/14566048/diff/51002/content/cover.article
> File content/cover.article (right):
>
>
https://codereview.appspot.com/14566048/diff/51002/content/cover.article#newc...
> content/cover.article:2: 14 Nov 2013
> Let's make this "2 Dec 2013" or "3 Dec 2013"
>
> https://codereview.appspot.com/14566048/

[adg, 2013-12-02 20:59:04]

*** Submitted as
https://code.google.com/p/go/source/detail?r=b1bdd3bd1144&repo=blog ***

go.blog/cover: new article about test coverage

R=adg
https://codereview.appspot.com/14566048

Committer: Andrew Gerrand <adg@golang.org>

[r, 2014-01-23 23:43:21]

*** Abandoned ***