Neo4j Testing

[lindajiawenli]

For writing Neo4j Tests

Possible Tests (work in progress)

• 1. Verify DB connection with Neo4j driver
• 2. Verify 1 node is being made correctly
• 3. Verify 1 edge is being made correctly
• 4. Verify that attempting to make a duplicate node fails
• 5. Verify that attempting to make a duplicate edge fails
• 6. Verify that searchByGeneId function/read database is correct
• 7. Verify that all the nodes in a document are made (no duplication or missing nodes)
• 8. Verify that all the edges in a document are made (no duplication or missing nodes)
• 9. Verify that all the nodes in multiple documents are made (no duplication or missing nodes)
• 10. Verify that all the nodes in multiple documents are made (no duplication or missing nodes)
• 11. Verify that a node deletion is successful (function exists for testing, not sure if it is useful in our case)

refs #1122

[maxkfranz]

This looks like a good list to start. I'd start with a few of the ones at the top of the list, and then put up a PR to get feedback and plan next steps.

7-10 sound like good tests for later, once you start on the document-level functions. You probably had the same thing in mind, but it bears repeating: Here, it's best to do higher-level functions and tests after you've verified that the lower-level ones are OK.

Great that you're planning ahead.

[jvwong]

FYI you can create checklists in GitHub with Markdown:

• do this
• do that