Details
-
Type: Task
-
Status: In Progress
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Epic Link:
Description
Write tests that fetch a (hopefully stable) entry from a remote database and verify that Jalview can process it.
These would be annotated (groups="Network") as distinct from our standalone "Functional" tests.
The intention is to give early warning when remote services change behaviour.
As for example lately (but not limited to):
- format of ENA XML changed - Castor binding failed - unable to fetch EMBL sequence data
- Ensembl gff changed from "transcript" to "mRNA" for transcript feature type in gene features
These would be annotated (groups="Network") as distinct from our standalone "Functional" tests.
The intention is to give early warning when remote services change behaviour.
As for example lately (but not limited to):
- format of ENA XML changed - Castor binding failed - unable to fetch EMBL sequence data
- Ensembl gff changed from "transcript" to "mRNA" for transcript feature type in gene features
Attachments
Issue Links
- related with
-
JAL-2482 Error in the latest SIFTS Update - some residues' RESNUM are assigned "null" string
- Closed
-
JAL-2485 Exception while querying Uniprot via the REST API
- Closed
-
JAL-2254 Fetch DBRefs from EMBL gives Illegal Text data found as child of: ROOT
- Closed
-
JAL-2245 (unannounced) changes to ENA 1.2 XML format
- Closed