Exercise 1: Maps
- In MovieDB, add a new field “Principal filming location”.
- In a movie’s show view, geocode that location and show a Google map centered around it
- Now write an E2E feature that tests that the map shows the correct location.
Hints
- The purpose of this lesson to learn interacting with external APIs from JavaScript. Even though this exercise can be implemented trivially by embedding a
Google Maps iframe
Show archive.org snapshot
, don't do that for the purpose of learning. Instead you should work with JavaScript-consumable APIs, either by calling functions of a client library or by making your own HTTP requests using
fetch()
or AJAX.
- To implement this exercise you will need two external services: One to transform an address string to geographical coordinates ("geocoding") and one to display a map centered around given coordinates.
- Google Maps offers both geocoding and map display APIs. If you want to use Google Maps, you need to sign up for an API key.
- A free alternative for educational use is using
Leaflet.js
Show archive.org snapshot
with an
OpenStreetMap Tile Provider
Show archive.org snapshot
. You can geocode an address with the
Nominatim API
Show archive.org snapshot
(it supports CORS requests).
- If you have trouble displaying the marker Icon, ask your mentor for help. It's a bit tricky to get the fingerprinted image from esbuild into the leaflet configuration.
- Your JavaScript that creates and centers the map should expose an API that lets you query the current map position from your test.
- Your test can use
evaluate_script(...)
Show archive.org snapshot
to talk with that JavaScript.
Exercise 2: Gender API
- In MovieDB, add a field "gender" to the
Actor
model.
- In the actor form automatically suggest a gender as the user types a name
- Also read this card for an issue you might encounter.
- The user should be able to override the suggestion.
- Use
https://gender-api.com/
Show archive.org snapshot
for this.
Testing
Write an E2E feature that tests the functionality above. Implement the test using two different techniques:
- Actually talk to the Gender API during tests.
- Only in tests, replace the JavaScript function that talks to the Gender API, with a fake implementation that maps a fixed list of names to their genders.
- It should have the same API as your original Gender API client.
- The fixed list of names can be part of your fake implementation. If it helps your test, your fake implementation might also expose an additional API to change the list of names.
Talk with your mentor about the pros and cons of each approach.
Tip
Use feature flags to disable the gender autosuggestion and map rendering in tests. Enable each feature only for tests that actually care about the corresponding functionality.
Posted by Henning Koch to makandra Curriculum (2015-08-20 14:33)