Draft Acceptance tests - Githubissues

ODIQueensland / ckan-data-curator-integration

A place to plan, collect issues and store items that support integrating Data Curator with CKAN

MIT License

1 stars 0 forks source link

Draft Acceptance tests #16

Open Stephen-Gates opened 6 years ago

Stephen-Gates commented 6 years ago

Acceptance tests are stored in GitHub and published on Cucumber Pro

This issue is to create a first draft. Acceptance tests are expected to be refined as the implementation approach is confirmed. Areas we're expecting changes in are:

Table Schema
CSV Dialects
Metadata mapping (especially where data or metadata is supported in one system and not the other)
Bringing other CKAN extensions to create a better experience, e.g.
- CKAN Validation extension
- CKAN Scheming extension

Stephen-Gates commented 6 years ago

@mattRedBox picking up on https://github.com/ODIQueensland/ckan-data-curator-integration/issues/30#issuecomment-396138913 I'm happy to add mapping examples to the acceptance tests but not 100% sure on the best way in gherkin

Import and Download features

provide datapackage.json upload file inline?
provide datapackage.zip upload - link to .zip?
how should I show how the data and metadata is stored in CKAN?

ghost commented 6 years ago

Hi @Stephen-Gates Don't have to add examples to gherkin necessarily - I can always do this later given time, but even if in github issue, similar to the reference I put in in #30 , that way I have something clearer about what needs to be re-mapped. Otherwise I'll put something together in Data Curator and import and export from there.

louisjasek commented 6 years ago

I think the acceptance criteria are mostly good. I am keen to run through the mapping to make get a sense of our level of confidence though. I'll keep doing a bit of analysis on my end to make sure I'm comfortable with it.

ghost commented 6 years ago

Hi @louisjasek There are additions to be made to this document as I work through code - but also as the code is pushed up to frictionless and they decide whether choices made fit with their vision for the libraries we are updating. I'll update this document as I work through these issues and the estimates for you. Some of the more difficult mappings may not be addressed immediately because of our interactions with frictionless, and issues that arise when edge cases are discovered.

louisjasek commented 6 years ago

No worries thanks Matt - I'm keen to stay across the detail on this as it develops

ghost commented 6 years ago

Hi @louisjasek No problem