Skip to content
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

Additional tests for get_regional_data #302

Open
2 of 8 tasks
RichardMN opened this issue Apr 21, 2021 · 9 comments
Open
2 of 8 tasks

Additional tests for get_regional_data #302

RichardMN opened this issue Apr 21, 2021 · 9 comments
Labels
enhancement New feature or request no-issue-activity

Comments

@RichardMN
Copy link
Collaborator

RichardMN commented Apr 21, 2021

Working through #119 we've hit some odd problems with the data coming out of the end of our pipe and I think @seabbs asked how we could have detected them earlier.

Here are some possible tests, likely to be applied to get_regional_data output, not on CRAN, but possibly as part of our regular nightly dataset sanity checking.

These should probably be run with localisation of regions off to make it easier to write generically. They will also rely in some places on comparing output at level 1 with output at level 2.

@RichardMN RichardMN added the enhancement New feature or request label Apr 21, 2021
@seabbs
Copy link
Contributor

seabbs commented Apr 22, 2021

This all looks pretty spot on. I can look at this this weekend/next week.

@joseph-palmer
Copy link
Collaborator

I've made a start with a couple of them, I will open an additional tests PR to load these into and if anyone else does any just merge into that PR :)

@joseph-palmer
Copy link
Collaborator

I think it's a good idea to run these nightly as many will need to work on the full downloaded dataset rather than the snapshot. Can anyone tell me how to ensure a test only runs on this?

@seabbs
Copy link
Contributor

seabbs commented May 5, 2021

In my mind the get_ functions and friends should be tested and documented in a dataset independent way with dataset tests happening elsewhere. I've updated the title of this issue to reflect this.

@github-actions
Copy link

github-actions bot commented Jul 5, 2021

This issue has been flagged as stale due to lack of activity

@seabbs seabbs reopened this Jul 12, 2021
@seabbs seabbs reopened this Jul 20, 2021
@seabbs seabbs reopened this Jul 28, 2021
@github-actions github-actions bot closed this as completed Aug 5, 2021
@seabbs seabbs reopened this Aug 5, 2021
@seabbs
Copy link
Contributor

seabbs commented Aug 6, 2021

This has got a bit stuck. What do we think still needs doing vs nice to have here?

@RichardMN
Copy link
Collaborator Author

It's stuck. I might be able to take over @joseph-palmer's PR #307 or just embed it into #312 and try to bring it up to speed with the rest of the package. I don't think I'd do it better but I know this is something which I might be able to do and free up efforts for elsewhere.

@github-actions
Copy link

github-actions bot commented Oct 6, 2021

This issue has been flagged as stale due to lack of activity

@github-actions
Copy link

github-actions bot commented Apr 7, 2022

This issue has been flagged as stale due to lack of activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request no-issue-activity
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants