testing: added build tags to large test geometries

[ear7h]

The changes in this pull request are actually part of #69 but I don't see that PR being merged soon (it's complicated and there's bigger fish to fry) but, I'd really like this patch so that tests can be compiled/run in a reasonable amount of time.

The only changes in this PR are build tags to the files which contain or organize tiles in the testing directory.

[coveralls]

Pull Request Test Coverage Report for Build 313

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 58.009%

---

Totals
Change from base Build 287:	0.0%
Covered Lines:	17286
Relevant Lines:	29799

---

💛 - Coveralls

[gdey]

I have not reviewed this, but just from the description, this is the wrong direction. There are already command lines params for running quick tests and the testing support for this. We should be using t.Skip and t.Short() for this type of things. Then on the command line do: go test -short for quicker tests.

[ARolek]

@gdey this is a really small PR, can you give it another look? I'm not quite sure if t.Skip() or t.Short() would be appropriate here. I think the main issue that @ear7h is trying to address is skipping the compiler from including these geometries unless the developer is explicitly interested in working on them.

[gdey]

What are you trying to do with this PR? What is the problem you are trying to address? Adding the build tag will force any tests that is making use of these cases to include that tag as well, otherwise, things will not compile.

[ear7h]

@gdey The goal is what @ARolek mentioned. The files that I added the build tags to are >100MB together and compiling them takes an unnecessarily long time since the geometries end up not being used in tests. This PR is especially helpful for CI because it runs go test .;/... 6 times with no build cache each time.

Here's the output from time for the two branches:

master $ CGO_ENABLED=0 time go test ./...
...
       71.32 real       120.84 user        12.42 sys

test-tile-tag $ CGO_ENABLED=0 time go test ./...
...
        9.33 real        25.04 user         5.11 sys

[ear7h]

After some discussion, we found the best solution would be to decode the geometry at runtime, storing it as a string in source code. This would prevent odd bugs from using build tags while keeping the compilation speed of tests relatively quick.

I've implemented a patch on top of what's sitting in the wkt: improvements PR. And it's slightly more complicated than expected, because we cannot have the circular dependency wkt -> testing ->wkt. But, I don't think this is a problem because it communicates the need for a compilation step rather than mindlessly accessing gtesting.Tiles() (this might lead to bugs when running benchmarks).

[gdey]

@ear7h did you get all the package tests passing?

[gdey]

LGTM