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

Start doing Behavior Test Driven Design for Version 2 #46

Open
wants to merge 18 commits into
base: use-cases-docs
Choose a base branch
from

Conversation

kdallmeyer-sr
Copy link
Contributor

Added a submodule that contains some use-case tests for version 2. The tests fail on purpose as only the skeleton functions are defined. The hope is to first iterate over the use-cases and the Baleen DSL before jumping into implementation.

dependabot-preview bot and others added 16 commits July 5, 2019 13:54
ShopRunner#50)

The last occurrance was the only one returned to the validator
This has a fix for the version of kotlinter 2.0 which dependabot has a pull request today.
What use cases does Baleen solve? What use cases are _not_ the right fit?
"Given we have the data, we define the Baleen schema manually and validate the data"
"Given we have the data, we learn the Baleen schema and validate the data"
"Given a external schema (Avro, XSD, Json-Schema, Kotlin data class), build Baleen schema and validate the data"
"Given a Baleen schema, create external schema (Avro, XSD, Json-Schema, Kotlin data class) and validate the data with the external schema"
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