Skip to content

Improve tests for table types #143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 28, 2021
Merged

Conversation

molpopgen
Copy link
Member

@molpopgen molpopgen commented Jul 21, 2021

In light of the new row ID types introduced recently (see #128), this PR adds a lot of tests to the various "tables" files.
These tests have:

  • Improved code coverage
  • Improved test organization (I think/hope)
  • Found and fixed some API issues
  • Created redundancy with previous tests.

Removing/reducing redundant tests can be handled in a follow-up PR. That follow up can maybe also add more of what we need, which is detailed checks of all the various Option inputs, etc., and how they affect table row equality comparisons, etc..

@molpopgen molpopgen force-pushed the add_tests_for_strong_ID_types branch from 9fa7803 to 504fa6f Compare July 21, 2021 22:49
@molpopgen molpopgen changed the title add tests for strong ID types Improve tests for table types Jul 27, 2021
collections":

* Add generic metadata fixture.
* Add missing Iterator implementations for IndividualTableIterator
  and IndividualTableRefIterator.
* TableCollection::add_migration_* now return Result<MigrationId, TskitError>.
* Fix bug where MigrationTable::node and MigrationTable::source were
  accessing the wrong C arrays.
@molpopgen molpopgen force-pushed the add_tests_for_strong_ID_types branch from a8f4f33 to 345b164 Compare July 28, 2021 15:36
@molpopgen molpopgen merged commit 86df702 into main Jul 28, 2021
@molpopgen molpopgen deleted the add_tests_for_strong_ID_types branch July 28, 2021 15:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant