Simple tests that will render a raster and a vector map and
hopefully the valgrind bot will detect something wrong if any.
The other test will look for application lifetime leaks that cannot
be detected with valgrind. It can also detect GL leaks if they are
very expressive. A threshold is needed because of memory will grow
anyway due to fragmentation.
The StupFileSource of the memory test will do the rendering
completely offline with a vector tile that is densly populated
with features and a raster tile of the same region.
The styles are streets and satellite respectivelly.
Now it works more like StubStyleObserver: you can assign std::functions to specific slots based on resource type.
Rewrite resource loading tests in that style, making them less like integration tests of Style and more like unit tests of Source, GlyphStore, and SpriteStore.
- MockFileSource
Will load pre-defined resources from the filesystem. It supports
passing a string, that when it matches an URL, will simulate a failure.
- MockView
It is just a no-op to not get in the way when testing
resource loading.
Few more additions:
- style.json
Specially crafted style that will look always for the same tile,
glyph range, etc at the "test/fixtures/resources/" path. No matter
where you look (or at what zoom), you always get the same stuff.
- vector.pbf
This taken from a part of Taipei that will request several glyph
ranges.
