geoblacklight 3.2.0 → 4.0.0.pre.alpha

data/schema/geometry-type-values.md

@@ -1,11 +0,0 @@
-## Geometry Type Vocabulary
-
-| Label | Icon Link | Definition|
-|:----------------------------|:-------------|:---------------------------------------------------------|
-|Point|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/point.svg)|Geospatial dataset made up of pairs of x,y coordinates|
-|Line|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/line.svg)|Geospatial dataset made up of straight or curved connected x,y coordinates|
-|Polygon|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/polygon.svg)|Geospatial dataset made up of closed connections of x,y coordinates|
-|Image|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/image.svg)|Static born-digital maps and scanned map images|
-|Raster|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/raster.svg)|Geospatial dataset that is presented as an array of cells comprised of single or multiple bands|
-|Mixed|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/mixed.svg)|Geospatial dataset with multiple geometry types|
-|Table|[Icon](https://github.com/geoblacklight/geoblacklight-icons/blob/master/graphics/table.svg)|Nonspatial dataset as a text file with delimiter separated values|

data/schema/references.md

@@ -1,23 +0,0 @@
-# External References
-
-The field `dct_references_s` defines external services and references using the [CatInterOp](https://github.com/OSGeo/Cat-Interop) approach. The field value is a serialized JSON array of key/value pairs, with keys representing XML namespace URI's and values the URL.
-
-Type | Reference URI | Enables in GeoBlacklight
-|:---- |:------------- |:------------------------|
-Web Mapping Service (WMS) | `http://www.opengis.net/def/serviceType/ogc/wms` | Layer preview, layer preview feature inspection, downloads (vector: KMZ, raster: GeoTIFF)|
-Web Feature Service (WFS) | `http://www.opengis.net/def/serviceType/ogc/wfs` | Vector downloads in GeoJSON and Shapefile|
-International Image Interoperability Framework (IIIF) Image API | `http://iiif.io/api/image` | Image viewer using [Leaflet-IIIF](https://github.com/mejackreed/Leaflet-IIIF)|
-Direct download file | `http://schema.org/downloadUrl` | Direct file download feature|
-Data dictionary / documentation download | `http://lccn.loc.gov/sh85035852` | Direct documentation download link|
-Full layer description | `http://schema.org/url` | Further descriptive information about layer|
-Metadata in ISO 19139 | `http://www.isotc211.org/schemas/2005/gmd/` | Structured metadata in ISO standard expressed as XML|
-Metadata in FGDC | `http://www.opengis.net/cat/csw/csdgm` | Structured metadata in FGDC standard expressed as XML|
-Metadata in MODS | `http://www.loc.gov/mods/v3` | Structured metadata in MODS format|
-Metadata in HTML | `http://www.w3.org/1999/xhtml` | Structured metadata in any standard expressed as HTML|
-ArcGIS FeatureLayer | `urn:x-esri:serviceType:ArcGIS#FeatureLayer` | Previewing of ArcGIS FeatureLayer Service|
-ArcGIS TiledMapLayer | `urn:x-esri:serviceType:ArcGIS#TiledMapLayer` | Previewing of ArcGIS TiledMapLayer Service|
-ArcGIS DynamicMapLayer | `urn:x-esri:serviceType:ArcGIS#DynamicMapLayer` | Previewing of ArcGIS DynamicMapLayer Service|
-ArcGIS ImageMapLayer | `urn:x-esri:serviceType:ArcGIS#ImageMapLayer` | Previewing of ArcGIS ImageMapLayer Service|
-Harvard Geospatial Library Email Download | `http://schema.org/DownloadAction` | Retrieve a file via email from the Harvard Geospatial Library|
-OpenIndexMap | `https://openindexmaps.org` | Provide an index map preview|
-oEmbed | `https://oembed.com` | Provide an object that is embeddable through an oEmbed service

data/schema/schema-commentary.md

@@ -1,198 +0,0 @@
-## Commentary and Suggestions for the GeoBlacklight 1.0 Metadata Schema
-
-This document elaborates on the application of fields in the
-GeoBlacklight 1.0 Metadata Schema with recommendations from the
-GeoBlacklight community of practice.
-
-For a profile of the schema, visit
-[here](/schema/geoblacklight-schema.md).
-
-### Identifier
-
-This field is required, but it is not displayed in the interface. It may
-be identical to the `layer_slug_s` field, or it may be related to or derived from the `layer_id_s`. This value is
-ideally a persistent identifier or permalink (such as a [PURL](https://en.wikipedia.org/wiki/Persistent_uniform_resource_locator) or [Handle](https://en.wikipedia.org/wiki/Handle_System).
-
-### Rights
-
-This field can be set to "Public", which allows users to view and
-download an item, or "Restricted", which requires a user to log in to an
-authentication service. If there are additional licenses or rights
-associated with a resource, administrators will have to create a custom field in the local Solr schema.
-
-### Title
-
-The title is the most prominent metadata field that users see when
-browsing or scanning search results. Since many datasets are created
-with ambiguous or non-unique titles, it may be worth the effort to
-improve or enhance them. The ideal sequence of a title is something akin
-to Topic of Layer: Place, Year. Putting the year at the end of a title
-produces better search results, since titles are left-anchored.
-
-### Provenance
-
-This field indicates the institution that contributed the resource. The
-current community of practice is for this field to hold the name of the
-university or institution that has created the GeoBlacklight metadata
-record and/or hosts the dataset. Projects are encouraged to submit their
-institutional icon to the GeoBlacklight Icons repository to display with the resource.
-
-### Schema Version
-
-"1.0" is the current version of the GeoBlacklight schema.
-
-### Slug
-
-The slug makes up the URL for the resource in GeoBlacklight. If having a
-readable slug is desired, it is common to use the form,
-institution-keyword1-keyword2 (words or characters are separated by hyphens).
-
-### Bounding Box
-
-The rectangular bounding box is to aid searching with the map interface.
-Although accuracy is encouraged, it may not always be necessary to to
-have precise bounding coordinates. The field functions to facilitate discovery more than to indicate exact extents.
-
-### Solr Year
-
-This field is a four digit integer that must be inferred by the temporal
-coverage or date issued of the resource. If a single record spans multiple years, choose the earliest year for the `solr_year_i` field.
-
-### Creator
-
-The `dc_creator_sm` field is best reserved for instances in which an
-individual person has collected, produced, or generated analyses of
-data (as opposed to an agency releasing a data product or resource). See also the comments on `dc_publisher_sm`.
-
-### Description
-
-The `dc_description_s` field is the second most prominent value that users see
-when search or browsing for items. Although not required, it is strongly
-recommended. If the description is minimal or lacking, it can be
-improved by concatenating available metadata fields, such as title,
-date, format, and place. This is a plain text field, so html code is not
-supported here unless the application is customized. It is recommended to assume that discovery happens in multiple contexts (i.e., GeoBlacklight metadata may be integrated into other discovery environments), so descriptions should use complete sentences that signpost what the data object is, even though that is evident within GeoBlacklight itself.
-
-### Format
-
-A long list of formats is available [here.](/schema/format-values.md)
-The most important thing to remember about the `dc_format_s` field is that it is
-required for Download functionality. Whatever value is in the `dc_format_s`
-field will show up as text in the Download widget, unless the application has local customizations.
-
-### Language
-
-This field is intended to indicate the language of the dataset, map,
-and/or supporting documentation. The most common practice in this community
-is to spell the name language out in English (e.g., "French").
-
-### Publisher
-
-The distinction between `dc_publisher_sm` and `dc_creator_sm` for data
-is often vague. Publishers should be the administrative body or
-organization that made the original resource available, regardless of
-who compiled or produced the data.
-
-### Source
-
-The `dc_source_sm` field exists to indicate parent-child relationships between
-records. Common uses include: individual sheets within a map series that
-can point to a Shapefile that serves as an index map, individual
-Shapefile layers that have been derived from a Geodatabase that can
-point to the record for the GeoDatabase, or collection-level and related
-individual layer records. See
-https://github.com/geoblacklight/geoblacklight/wiki/Using-data-relations-widget for more information.
-
-### Subject
-
-This field is indexed as a facet by default for GeoBlacklight
-applications, and it can become unwieldy when aggregating metadata
-records from multiple sources. Controlled vocabularies for GIS data have
-typically been expressed as ISO Topic Categories and localized thesauri,
-while scanned maps are typically described with Library of Congress
-Subject Headings. Even within these vocabularies, localized spellings
-and abbreviations will result in considerable variations between
-institutions. Institutions are encouraged to observe what terms are
-commonly in use and, at the very least, strive for internal consistency
-with controlled vocabularies and spellings. This facilitates easier
-metadata sharing across projects, such as the repositories in
-[OpenGeoMetadata](https://github.com/OpenGeoMetadata). Some institutions
-choose to create custom keyword fields to hold local, unnormalized
-values. It is recommended not to use Library of Congress Subject Headings to indicate the geography or spatial coverage of a dataset; instead, use the `dct_spatial_sm` field for this.
-
-### Type
-
-The `dc_type_s` field is optional, but it can be useful for categorizing
-between datasets, scanned maps, and collections. The GeoBlacklight schema
-observes the Dublin Core controlled vocabulary for [Type](/schema/type-values.md).
-
-### Is Part Of
-
-The `dct_isPartOf_sm` field is most often used as a way to group
-collections arbitrarily. Such groupings often have meaning within local
-institutions and can be shorthand for keeping like items
-together. For example, the value could mark all of the items in a single
-data submission, all of the items that pertain to a class that is
-working with GIS data, or all of the items harvested from a specific
-Open Data portal.
-
-### Date Issued
-
-Although the `dct_issued_s` field is optional, it is often useful when
-a clear Temporal Coverage value is not present. For example, one may
-want to preserve a dataset with an uncertain lineage, but there is an
-indicator on a data portal on the date of last update.
-
-### References
-
-All of the external links for the resource are added to the `dct_references_s`
-field as a serialized JSON array of key/value pairs. For example:
-
-```
-<field name="dct_references_s">
-  {
-    "http://schema.org/url":"http://purl.stanford.edu/bb509gh7292",
-    "http://schema.org/downloadUrl":"http://stacks.stanford.edu/file/druid:bb509gh7292/data.zip",
-    "http://www.loc.gov/mods/v3":"http://purl.stanford.edu/bb509gh7292.mods",
-    "http://www.isotc211.org/schemas/2005/gmd/":"http://opengeometadata.stanford.edu/metadata/edu.stanford.purl/druid:bb509gh7292/iso19139.xml",
-    "http://www.w3.org/1999/xhtml":"http://opengeometadata.stanford.edu/metadata/edu.stanford.purl/druid:bb509gh7292/default.html",
-    "http://www.opengis.net/def/serviceType/ogc/wfs":"https://geowebservices-restricted.stanford.edu/geoserver/wfs",
-    "http://www.opengis.net/def/serviceType/ogc/wms":"https://geowebservices-restricted.stanford.edu/geoserver/wms"
-  }
-</field>
-```
-See the [References controlled vocabulary](/schema/references.md) for the URIs of the keys and their recommended uses.
-
-### Spatial Coverage
-
-It is recommended to have at least one place name for each layer that
-corresponds to the logical extent of the area of that layer. Adding
-additional place names that fall within the layer should be done only if
-they are topically relevant to the content of the data. If a long list of
-place names is desired in the metadata for search purposes, a customized
-hidden field is recommended.
-
-### Temporal Coverage
-
-The `dct_temporal_sm` field is multi-valued, so multiple strings can be used to indicate the time period the resource depicts, when the
-data was collected, and/or when the resources was created. Examples include: “1910?”, “1800-1805”, “before 2000”. If a single dataset spans multiple years, one can add each intervening year as a discrete value (e.g., 2007,2008,2009,2010). However, a common convention is to include only the first and last year (e.g., 2007,2010 for a dataset encompassing the span of time between 2007 and 2010).
-
-###  Geometry Type
-
-This field helps to differentiate between vector (Point, Line, Polygon),
-raster (Raster, Image), nonspatial formats (table), or a combination
-(Mixed). If processing metadata from a geospatial web server, this value
-may be programmatically determined. However, in many cases, it must be manually
-determined. The field is tied to icons for the resource, and provides
-the user with visual clues to the item. However, if the element is
-troublesome or unnecessary for a particular institution, it can be
-omitted. [See the controlled vocabulary.](/schema/geometry-type-values.md)
-
-### Layer ID
-
-The Layer ID is used to point to specific layers within a geospatial web
-service. This field is not used for ArcGIS Rest Services.
-
-### Modified Date
-
-This value should indicate when the metadata (not the resource itself) was last modified.

data/schema/subjects.md

@@ -1,41 +0,0 @@
-These charts lists the most common terms and spellings for Subjects
-in the GeoBlacklight community.
-
-## Geospatial Data
-
-Common spelling | Related terms
-|----|-------------
-Farming | Agriculture
-Biota | Biology |ISO Topic Category
-Boundaries | Administrative and political boundaries; Cities and towns
-Climatology, Meteorology, and Atmosphere | Climate
-Economy
-Elevation
-Environment |
-Geoscientific Information | Geology
-Health ||
-Imagery and Base Maps | Imagery; Basemaps; Landcover
-Intelligence and Military |
-Inland Waters |
-Location |
-Oceans |
-Planning and Cadastral | Property
-Society |
-Structure | Facilities and Structures
-Transportation |
-Utilities and Communications | Utilities
-
-## Maps
-
-Common spelling | Related terms
-|:---- |:------------- |
-Aeronautical charts
-Atlases
-Bathymetric maps
-Cadastral maps
-Fire insurance maps
-Geological maps
-Road maps
-Thematic maps
-Topographic maps
-Tourist maps

data/schema/type-values.md

@@ -1,10 +0,0 @@
-## GeoBlacklight Type Values
-
-| Label | Dublin Core Link | Definition|
-|:----------------------------|:-------------|:---------------------------------------------------------|
-|Dataset|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-Dataset)|Data encoded in a defined structure. Includes geospatial formats as vector, raster, and tabular data.|
-|Image|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-Image)|A visual representation other than text. Includes static born-digital maps, scanned map images, and aerial photography.|
-|Collection|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-Collection)|An aggregation of resources. Describes a group of resources that may or may not be separately described.|
-|Interactive Resource|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-InteractiveResource)|External web applications that require the user to input information to generate a filtered dataset|
-|Collection|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-Collection)|An aggregation of resources. Describes a group of resources that may or may not be separately described.|
-|Physical Object|[DCMI Link](http://dublincore.org/documents/dcmi-terms/#dcmitype-PhysicalObject)|Non-digital resource, such as a paper map or a globe|

data/spec/fixtures/solr_documents/metadata_no_dct_provenance_s.json

@@ -1,30 +0,0 @@
-{
-  "geoblacklight_version": "1.0",
-  "layer_modified_dt": "2019-12-16T15:57:35Z",
-  "layer_slug_s": "99-0001-noProvenance",
-  "dc_identifier_s": "99-0001-noProvenance",
-  "dc_title_s": "Social Explorer",
-  "dct_temporal_sm": [
-    "1790-present"
-  ],
-  "dc_description_s": "Requires creating a free account or logging in through an organization with licensed access. This interactive website includes the entire US census history from 1790 to 2000, the American Community Survey (ACS), and the Religious Congregations and Membership Study (RCMS) from 1980 to 2000? the most complete census available on religion in the U.S. Overall, the site contains 39 billion data points, 200,000 variables, and 15,000 interactive maps",
-  "dc_subject_sm": [
-    "Society"
-  ],
-  "dc_type_sm": [
-    "Interactive Resource"
-  ],
-  "dc_rights_s": "Restricted",
-  "layer_geom_type_s": "Table",
-  "solr_geom": "ENVELOPE(-179.9,-64.4,71.6,-14.8)",
-  "dc_publisher_sm": [
-    "Social Explorer"
-  ],
-  "dc_creator_sm": [
-    "Queens College (New York, N.Y.). Department of Sociology"
-  ],
-  "dct_spatial_sm": [
-    "United States"
-  ],
-  "dct_references_s": "{\"http://schema.org/url\":\"https://www.socialexplorer.com/\"}"
-}

data/spec/fixtures/solr_documents/metadata_no_layer_geom_type_s.json

@@ -1,17 +0,0 @@
-{
-  "geoblacklight_version": "1.0",
-  "layer_modified_dt": "2020-01-17T15:31:30Z",
-  "layer_slug_s": "05d-03-noGeomType",
-  "dc_identifier_s": "05d-03-noGeomType",
-  "dc_title_s": "University of Minnesota Digital Conservancy DRUM",
-  "dc_description_s": "DRUM is a publicly available collection of digital research data generated by University of Minnesota researchers, students, and staff. Anyone can search and download the data housed in the repository, instantly or by request.",
-  "dc_publisher_sm": [
-    "University of Minnesota Digital Conservancy"
-  ],
-  "dc_type_sm": [
-    "Collection"
-  ],
-  "dct_provenance_s": "Minnesota",
-  "dc_rights_s": "Public",
-  "dct_references_s": "{\"http://schema.org/url\":\"https://conservancy.umn.edu/handle/11299/166578\"}"
-}

data/spec/fixtures/solr_documents/metadata_no_solr_geom.json

@@ -1,23 +0,0 @@
-{
-  "geoblacklight_version": "1.0",
-  "layer_modified_dt": "2020-01-23T14:01:19Z",
-  "layer_slug_s": "05d-p16022coll246-noGeo",
-  "dc_identifier_s": "05d-p16022coll246-noGeo",
-  "dc_title_s": "Ames Library of South Asia Maps",
-  "dc_description_s": "A collection of maps covering Asia held by the University of Minnesota's Ames Library of South Asia.",
-  "dc_publisher_sm": [
-    "University of Minnesota"
-  ],
-  "dc_type_sm": [
-    "Collection"
-  ],
-  "layer_geom_type_s": "Table",
-  "dct_provenance_s": "Minnesota",
-  "dct_spatial_sm": [
-    "Asia",
-    "India",
-    "Afghanistan"
-  ],
-  "dc_rights_s": "Public",
-  "dct_references_s": "{\"http://schema.org/url\":\"https://umedia.lib.umn.edu/search?facets[collection_name_s][]=Ames+Library+of+South+Asia+Maps\"}"
-}

data/spec/javascripts/geoblacklight/viewers/esri/tiled_map_layer_spec.js

@@ -1,12 +0,0 @@
-//= require geoblacklight
-
-describe('setupInspection', function() {
-  describe('Inspect attribute on the map', function() {
-    it('identifyFeatures is defined', function() {
-      expect(L.esri.identifyFeatures).toBeDefined();
-    });
-    it('Tasks is not defined', function() {
-      expect(L.esri.Tasks).toBeUndefined();
-    });
-  });
-});

data/spec/javascripts/spec_helper.js

@@ -1,32 +0,0 @@
-// Teaspoon includes some support files, but you can use anything from your own support path too.
-// require support/jasmine-jquery-1.7.0
-// require support/jasmine-jquery-2.0.0
-// require support/jasmine-jquery-2.1.0
-// require support/sinon
-// require support/your-support-file
-//
-// PhantomJS (Teaspoons default driver) doesn't have support for Function.prototype.bind, which has caused confusion.
-// Use this polyfill to avoid the confusion.
-//= require support/bind-poly
-//
-// You can require your own javascript files here. By default this will include everything in application, however you
-// may get better load performance if you require the specific files that are being used in the spec that tests them.
-//= require application
-//
-// Deferring execution
-// If you're using CommonJS, RequireJS or some other asynchronous library you can defer execution. Call
-// Teaspoon.execute() after everything has been loaded. Simple example of a timeout:
-//
-// Teaspoon.defer = true
-// setTimeout(Teaspoon.execute, 1000)
-//
-// Matching files
-// By default Teaspoon will look for files that match _spec.{js,js.coffee,.coffee}. Add a filename_spec.js file in your
-// spec path and it'll be included in the default suite automatically. If you want to customize suites, check out the
-// configuration in teaspoon_env.rb
-//
-// Manifest
-// If you'd rather require your spec files manually (to control order for instance) you can disable the suite matcher in
-// the configuration and use this file as a manifest.
-//
-// For more information: http://github.com/modeset/teaspoon

data/spec/lib/geoblacklight/controller_override_spec.rb

@@ -1,2 +0,0 @@
-# frozen_string_literal: true
-require 'spec_helper'

data/spec/teaspoon_env.rb

@@ -1,214 +0,0 @@
-# frozen_string_literal: true
-unless defined?(Rails)
-  ENV['RAILS_ROOT'] = File.expand_path('../../', __FILE__)
-  require File.expand_path('../../config/environment', __FILE__)
-end
-
-# Teaspoon doesn't allow you to pass client driver options to the Selenium WebDriver. This monkey patch
-# is a temporary fix until this PR is merged: https://github.com/jejacks0n/teaspoon/pull/519.
-require 'teaspoon/driver/selenium'
-
-Teaspoon::Driver::Selenium.class_eval do
-  def run_specs(runner, url)
-    driver = ::Selenium::WebDriver.for(
-      driver_options[:client_driver],
-      **driver_options[:selenium_options].to_hash.to_options
-    )
-    driver.navigate.to(url)
-
-    ::Selenium::WebDriver::Wait.new(driver_options).until do
-      done = driver.execute_script('return window.Teaspoon && window.Teaspoon.finished')
-      driver.execute_script('return window.Teaspoon && window.Teaspoon.getMessages() || []').each do |line|
-        runner.process("#{line}\n")
-      end
-      done
-    end
-  ensure
-    driver&.quit
-  end
-end
-
-Teaspoon.configure do |config|
-  # Determines where the Teaspoon routes will be mounted. Changing this to "/jasmine" would allow you to browse to
-  # `http://localhost:3000/jasmine` to run your tests.
-  config.mount_at = '/teaspoon'
-
-  # Specifies the root where Teaspoon will look for files. If you're testing an engine using a dummy application it can
-  # be useful to set this to your engines root (e.g. `Teaspoon::Engine.root`).
-  # Note: Defaults to `Rails.root` if nil.
-  config.root = Geoblacklight::Engine.root
-
-  # Paths that will be appended to the Rails assets paths
-  # Note: Relative to `config.root`.
-  config.asset_paths = ['spec/javascripts', 'spec/javascripts/stylesheets']
-
-  # Fixtures are rendered through a controller, which allows using HAML, RABL/JBuilder, etc. Files in these paths will
-  # be rendered as fixtures.
-  config.fixture_paths = ['spec/javascripts/fixtures']
-
-  # SUITES
-  #
-  # You can modify the default suite configuration and create new suites here. Suites are isolated from one another.
-  #
-  # When defining a suite you can provide a name and a block. If the name is left blank, :default is assumed. You can
-  # omit various directives and the ones defined in the default suite will be used.
-  #
-  # To run a specific suite
-  # - in the browser: http://localhost/teaspoon/[suite_name]
-  # - with the rake task: rake teaspoon suite=[suite_name]
-  # - with the cli: teaspoon --suite=[suite_name]
-  config.suite do |suite|
-    # Specify the framework you would like to use. This allows you to select versions, and will do some basic setup for
-    # you -- which you can override with the directives below. This should be specified first, as it can override other
-    # directives.
-    # Note: If no version is specified, the latest is assumed.
-    #
-    # Versions: 1.3.1, 2.0.3, 2.1.3, 2.2.0
-    suite.use_framework :jasmine, '2.2.0'
-
-    # Specify a file matcher as a regular expression and all matching files will be loaded when the suite is run. These
-    # files need to be within an asset path. You can add asset paths using the `config.asset_paths`.
-    suite.matcher = '{spec/javascripts,app/assets}/**/*_spec.{js,js.coffee,coffee}'
-
-    # Load additional JS files, but requiring them in your spec helper is the preferred way to do this.
-    # suite.javascripts = []
-
-    # You can include your own stylesheets if you want to change how Teaspoon looks.
-    # Note: Spec related CSS can and should be loaded using fixtures.
-    # suite.stylesheets = ["teaspoon"]
-
-    # This suites spec helper, which can require additional support files. This file is loaded before any of your test
-    # files are loaded.
-    suite.helper = 'spec_helper'
-
-    # Partial to be rendered in the head tag of the runner. You can use the provided ones or define your own by creating
-    # a `_boot.html.erb` in your fixtures path, and adjust the config to `"/boot"` for instance.
-    #
-    # Available: boot, boot_require_js
-    suite.boot_partial = 'boot'
-
-    # Partial to be rendered in the body tag of the runner. You can define your own to create a custom body structure.
-    suite.body_partial = 'body'
-
-    # Hooks allow you to use `Teaspoon.hook("fixtures")` before, after, or during your spec run. This will make a
-    # synchronous Ajax request to the server that will call all of the blocks you've defined for that hook name.
-    # suite.hook :fixtures, &proc{}
-
-    # Determine whether specs loaded into the test harness should be embedded as individual script tags or concatenated
-    # into a single file. Similar to Rails' asset `debug: true` and `config.assets.debug = true` options. By default,
-    # Teaspoon expands all assets to provide more valuable stack traces that reference individual source files.
-    # suite.expand_assets = true
-  end
-
-  # Example suite. Since we're just filtering to files already within the root test/javascripts, these files will also
-  # be run in the default suite -- but can be focused into a more specific suite.
-  # config.suite :targeted do |suite|
-  #  suite.matcher = "spec/javascripts/targeted/*_spec.{js,js.coffee,coffee}"
-  # end
-
-  # CONSOLE RUNNER SPECIFIC
-  #
-  # These configuration directives are applicable only when running via the rake task or command line interface. These
-  # directives can be overridden using the command line interface arguments or with ENV variables when using the rake
-  # task.
-  #
-  # Command Line Interface:
-  # teaspoon --driver=phantomjs --server-port=31337 --fail-fast=true --format=junit --suite=my_suite /spec/file_spec.js
-  #
-  # Rake:
-  # teaspoon DRIVER=phantomjs SERVER_PORT=31337 FAIL_FAST=true FORMATTERS=junit suite=my_suite
-
-  # Specify which headless driver to use. Supports PhantomJS and Selenium Webdriver.
-  #
-  # Available: :phantomjs, :selenium, :capybara_webkit
-  # PhantomJS: https://github.com/modeset/teaspoon/wiki/Using-PhantomJS
-  # Selenium Webdriver: https://github.com/modeset/teaspoon/wiki/Using-Selenium-WebDriver
-  # Capybara Webkit: https://github.com/modeset/teaspoon/wiki/Using-Capybara-Webkit
-  config.driver = :selenium
-  config.driver_options = {
-    client_driver: :chrome,
-    selenium_options: {
-      options: Selenium::WebDriver::Chrome::Options.new(args: ['headless', 'disable-gpu'])
-    }
-  }
-
-  # Specify additional options for the driver.
-  #
-  # PhantomJS: https://github.com/modeset/teaspoon/wiki/Using-PhantomJS
-  # Selenium Webdriver: https://github.com/modeset/teaspoon/wiki/Using-Selenium-WebDriver
-  # Capybara Webkit: https://github.com/modeset/teaspoon/wiki/Using-Capybara-Webkit
-  # config.driver_options = nil
-
-  # Specify the timeout for the driver. Specs are expected to complete within this time frame or the run will be
-  # considered a failure. This is to avoid issues that can arise where tests stall.
-  # config.driver_timeout = 180
-
-  # Specify a server to use with Rack (e.g. thin, mongrel). If nil is provided Rack::Server is used.
-  # config.server = nil
-
-  # Specify a port to run on a specific port, otherwise Teaspoon will use a random available port.
-  # config.server_port = nil
-
-  # Timeout for starting the server in seconds. If your server is slow to start you may have to bump this, or you may
-  # want to lower this if you know it shouldn't take long to start.
-  # config.server_timeout = 20
-
-  # Force Teaspoon to fail immediately after a failing suite. Can be useful to make Teaspoon fail early if you have
-  # several suites, but in environments like CI this may not be desirable.
-  # config.fail_fast = true
-
-  # Specify the formatters to use when outputting the results.
-  # Note: Output files can be specified by using `"junit>/path/to/output.xml"`.
-  #
-  # Available: :dot, :clean, :documentation, :json, :junit, :pride, :rspec_html, :snowday, :swayze_or_oprah, :tap, :tap_y, :teamcity
-  # config.formatters = [:dot]
-
-  # Specify if you want color output from the formatters.
-  # config.color = true
-
-  # Teaspoon pipes all console[log/debug/error] to $stdout. This is useful to catch places where you've forgotten to
-  # remove them, but in verbose applications this may not be desirable.
-  # config.suppress_log = false
-
-  # COVERAGE REPORTS / THRESHOLD ASSERTIONS
-  #
-  # Coverage reports requires Istanbul (https://github.com/gotwarlost/istanbul) to add instrumentation to your code and
-  # display coverage statistics.
-  #
-  # Coverage configurations are similar to suites. You can define several, and use different ones under different
-  # conditions.
-  #
-  # To run with a specific coverage configuration
-  # - with the rake task: rake teaspoon USE_COVERAGE=[coverage_name]
-  # - with the cli: teaspoon --coverage=[coverage_name]
-
-  # Specify that you always want a coverage configuration to be used. Otherwise, specify that you want coverage
-  # on the CLI.
-  # Set this to "true" or the name of your coverage config.
-  # config.use_coverage = nil
-
-  # You can have multiple coverage configs by passing a name to config.coverage.
-  # e.g. config.coverage :ci do |coverage|
-  # The default coverage config name is :default.
-  config.coverage do |coverage|
-    # Which coverage reports Istanbul should generate. Correlates directly to what Istanbul supports.
-    #
-    # Available: text-summary, text, html, lcov, lcovonly, cobertura, teamcity
-    # coverage.reports = ["text-summary", "html"]
-
-    # The path that the coverage should be written to - when there's an artifact to write to disk.
-    # Note: Relative to `config.root`.
-    # coverage.output_path = "coverage"
-
-    # Assets to be ignored when generating coverage reports. Accepts an array of filenames or regular expressions. The
-    # default excludes assets from vendor, gems and support libraries.
-    # coverage.ignore = [%r{/lib/ruby/gems/}, %r{/vendor/assets/}, %r{/support/}, %r{/(.+)_helper.}]
-
-    # Various thresholds requirements can be defined, and those thresholds will be checked at the end of a run. If any
-    # aren't met the run will fail with a message. Thresholds can be defined as a percentage (0-100), or nil.
-    # coverage.statements = nil
-    # coverage.functions = nil
-    # coverage.branches = nil
-    # coverage.lines = nil
-  end
-end