Problem / Opportunity
Implement automated testing to check NWK string match.
Proposed Behavior
When NWK tree is used as an input, once 2D network is generated, if we go to phylogenetic tree view and check the tree, MT should be able to run tests to make sure the tree generated withing MT should exactly match the input NWK.
When NWK is used as input, MT uses patristic to back calculate distances to generate the network. For tree view, does it just display the tree based on reading the input NWK file, or does it build a NJ tree from the 2D network? If it merely displays the input tree, no need for comparison testing.
In fact, that is what the ideal behavior should be. If input is NWK, MT should act as a tree viewer, and not build.
User Value
Confidence in tree generation
Feature Area / View
2D plus Phylogeny
Inputs / Data Shape
NWK
Acceptance Criteria
Related Work
- Existing user story:
- Existing bug:
- Cypress coverage:
- Docs/manual:
Problem / Opportunity
Implement automated testing to check NWK string match.
Proposed Behavior
When NWK tree is used as an input, once 2D network is generated, if we go to phylogenetic tree view and check the tree, MT should be able to run tests to make sure the tree generated withing MT should exactly match the input NWK.
When NWK is used as input, MT uses patristic to back calculate distances to generate the network. For tree view, does it just display the tree based on reading the input NWK file, or does it build a NJ tree from the 2D network? If it merely displays the input tree, no need for comparison testing.
In fact, that is what the ideal behavior should be. If input is NWK, MT should act as a tree viewer, and not build.
User Value
Confidence in tree generation
Feature Area / View
2D plus Phylogeny
Inputs / Data Shape
NWK
Acceptance Criteria
Related Work