• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

MediaComem / biopocket-mobile
87%
master: 90%

Build:
Build:
LAST BUILD BRANCH: v1.0.0
DEFAULT BRANCH: master
Repo Added 06 Sep 2017 01:01PM UTC
Files 54
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH travis-test
branch: travis-test
CHANGE BRANCH
x
Reset
  • travis-test
  • angular-5-upgrade
  • devmel
  • e2e-backend
  • e2e-bbox-fix
  • http-client-update
  • i18n
  • integrating-mockups
  • markdown
  • master
  • observables-update
  • sprint-1-discovering-biodiversity
  • sprint-2-introducing-actions
  • story-152-registration
  • story-52-list-actions
  • story-55-action-details
  • story-56-theme-details
  • story-666-example
  • story-map-leaflet
  • story-poi-details
  • story-poi-on-map
  • task-center-map
  • temp-home-page
  • travis
  • tslint
  • v0.1.0
  • v0.1.1
  • v1.0.0

pending completion
147

push

travis-ci

AlphaHydrae
Replace legacy Http provider with HttpClient

Automated tests have had to be updated to the new way of mocking
requests, i.e. using `HttpClientTestingModule` and
`HttpTestingController`.

Formerly, `ApiService` was mostly a utility provider used by other
providers. Now, it's a provider like the others. The generic
functionality it managed (prepending the backend URL to request paths)
is now managed in the new `ApiInterceptorProvider`. Authentication
through the `Authorization` header will later be handled there as well.

Note that unit tests have also been made "more unitary":

* Unit tests for providers should mock HTTP responses, as HTTP calls are
  made in their implementation.
* Unit tests for components should NOT mock HTTP responses, as the calls
  are made in the services. The services themselves should be mocked
  instead. There should be no reason to mock HTTP responses in most (if
  not all) component tests.

The `ng-request-builder` dependency has been removed as it has been made
obsolete by the simpler interface of the new `HttpClient` provider.

An unrelated modification is that the `Geometry` submodel of the
`Location` model was modified to NOT reverse the longitude/latitude
coordinates provided by the API. Since `Geometry` has the same structure
as a GeoJSON point, it's counter-intuitive to not order the coordinates
in the same way. The reversal is done when creating the Leaflet markers
instead, since they use the latitude/longitude order.

Task: TG-107

19 of 32 branches covered (59.38%)

Branch coverage included in aggregate %.

189 of 207 relevant lines covered (91.3%)

4.23 hits per line

Relevant lines Covered
Build:
Build:
207 RELEVANT LINES 189 COVERED LINES
4.23 HITS PER LINE
Source Files on travis-test
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
147 travis-test Replace legacy Http provider with HttpClient Automated tests have had to be updated to the new way of mocking requests, i.e. using `HttpClientTestingModule` and `HttpTestingController`. Formerly, `ApiService` was mostly a utility provider used b... push 04 May 2018 10:46AM UTC AlphaHydrae travis-ci pending completion  
See All Builds (261)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc