Skip to content

test(api_018): export download/landing URLs must point at the env under test - #191

Open
saqibmanan wants to merge 2 commits into
CIfrom
test/export-public-urls
Open

saqibmanan wants to merge 2 commits into
CIfrom
test/export-public-urls

Conversation

@saqibmanan

Copy link
Copy Markdown
Contributor

The existing test_api_018 export tests only check the document's shape. So they stayed green while every dcat:downloadURL on dev pointed at api.civicdataspace.in, a host that doesn't resolve (DataSpaceBackend#238).

Added (read-only, so they also run on prod)

  • test_export_download_urls_resolve_on_this_backend: every download URL is on API_BASE_URL and returns 200.
  • test_export_landing_page_is_on_this_frontend: dcat:landingPage is on HOME_URL_DEV, i.e. the frontend paired with that backend.

Verified on dev

  • Before PUBLIC_API_URL/PUBLIC_SITE_URL were set, both failed for the right reason, e.g. download URL https://api.civicdataspace.in/... is not on the backend under test (https://dev.api.civicdataspace.in).
  • After setting them and recreating the container: 6/6 passed.
  • On prod they stay skipped (deployed_pr #211) until DataSpaceBackend#239 deploys. Prod's .env is already set, so they should pass there.

A failure here usually means the backend .env on the target box is missing one of those two variables.

… under test

The shape-only export tests stayed green while every dcat:downloadURL on
dev pointed at api.civicdataspace.in, which does not resolve. xfail until
DataSpaceBackend#238 is fixed and PUBLIC_API_URL/PUBLIC_SITE_URL are set.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant