Browse Source

update test narrative

The narrative to test missing dataset was confusing as the dataset (a "nextstrain community" URL) was invalid for a local auspice server but valid for the nextstrain.org server. Making it a clearly non-existing dataset URL makes it less confusing when testing functionality within nextstrain.org.
master
james hadfield 1 year ago
parent
commit
33d749dc85
  1. 4
      narratives/test_missing-dataset.md

4
narratives/test_missing-dataset.md

@ -5,9 +5,9 @@ dataset: "https://nextstrain.org/zika?d=map"
abstract: "This narrative defines a second dataset which is inaccessible by (locally running) auspice and should display an error."
---
# [Summary](https://nextstrain.org/community/andersen-lab/HCoV-19-Genomics-Nextstrain/hCoV-19/usa/sandiego?c=region&d=tree&legend=open&onlyPanels&p=full&sidebar=closed)
# [Summary](https://nextstrain.org/dataset-doesnt-exist?c=region&d=tree&legend=open&onlyPanels&p=full&sidebar=closed)
This slide defines a dataset that is not valid for a local auspice server (note: the community URL it defines is valid for the nextstrain.org server).
This slide defines a dataset that is not valid for a local auspice server.
We should see a red error notification alerting the user of this.
The displayed dataset should be zika, as that is what the YAML frontmatter defines.
I'm unsure of what the query (i.e. viz settings) should be.

Loading…
Cancel
Save