Format comments in tests

private_test.go

@@ -1,17 +1,15 @@
 // -----------------------------------------------------------------------------
 // (c) balarabe@protonmail.com                                      License: MIT
-// :v: 2019-05-09 17:16:11 6D81D1                 one-file-pdf/[private_test.go]
+// :v: 2019-05-12 17:01:26 D4C05C                 one-file-pdf/[private_test.go]
 // -----------------------------------------------------------------------------
 
 package pdf
 
-/*
-This file contains unit tests for internal methods/functions.
-
-To generate a test coverage report use:
-	go test -coverprofile cover.out
-	go tool cover -html=cover.out
-*/
+//  This file contains unit tests for internal methods/functions.
+//
+//  To generate a test coverage report use:
+//  	go test -coverprofile cover.out
+//  	go tool cover -html=cover.out
 
 import (
 	"fmt"

public_test.go

@@ -1,29 +1,27 @@
 // -----------------------------------------------------------------------------
 // (c) balarabe@protonmail.com                                      License: MIT
-// :v: 2019-05-06 06:21:42 02D016                  one-file-pdf/[public_test.go]
+// :v: 2019-05-12 17:01:26 1DAD5A                  one-file-pdf/[public_test.go]
 // -----------------------------------------------------------------------------
 
 package pdf_test
 
-/*
-This file provides the entry points to run unit tests on the public API.
-
-The actual unit test functions are implemented in a separate 'utest'
-package, each named after the PDF method it tests, and not prefixed
-with 'Test'. That is because utest has to be imported as a normal
-package. 'utest' is only imported here and only used for testing.
-
-The test files are kept in a separate folder to avoid cluttering
-this root folder. Every unit test is in a separate file named
-after the tested method.
-
-To test a single method or property, use:
-	go test --run Test_PDF_MethodName_
-
-To generate a test coverage report, use:
-	go test -coverprofile cover.out
-	go tool cover -html=cover.out
-*/
+//  This file provides the entry points to run unit tests on the public API.
+//
+//  The actual unit test functions are implemented in a separate 'utest'
+//  package, each named after the PDF method it tests, and not prefixed
+//  with 'Test'. That is because utest has to be imported as a normal
+//  package. 'utest' is only imported here and only used for testing.
+//
+//  The test files are kept in a separate folder to avoid cluttering
+//  this root folder. Every unit test is in a separate file named
+//  after the tested method.
+//
+//  To test a single method or property, use:
+//  	go test --run Test_PDF_MethodName_
+//
+//  To generate a test coverage report, use:
+//  	go test -coverprofile cover.out
+//  	go tool cover -html=cover.out
 
 import (
 	"testing"