In order to test various aspects of the client code, we will need real data. It may be useful to coordinate with the other 3DBeacon teams to agree on a test set to make sure we all check for issues with "standard" data, and known "edge case" data (UniProtKB identifiers, PDB files, etc).
Essentially having a mini database (eg a json file) of identifiers pointing to example files that can be checked in tests.
Useful to keep track of why they are in the test set (eg "very large sequence", "weird insert characters", "missing structural residues", ...).
In order to test various aspects of the client code, we will need real data. It may be useful to coordinate with the other 3DBeacon teams to agree on a test set to make sure we all check for issues with "standard" data, and known "edge case" data (UniProtKB identifiers, PDB files, etc).
Essentially having a mini database (eg a json file) of identifiers pointing to example files that can be checked in tests.
Useful to keep track of why they are in the test set (eg "very large sequence", "weird insert characters", "missing structural residues", ...).