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

Add Continuous Integration support #17

Open
stefanw opened this issue Aug 9, 2012 · 1 comment
Open

Add Continuous Integration support #17

stefanw opened this issue Aug 9, 2012 · 1 comment
Labels

Comments

@stefanw
Copy link
Member

stefanw commented Aug 9, 2012

CI is awesome, but how to test laws? Some ideas:

  • Law Integrity: do all referenced laws exist? Is the referenced paragraph still existant?
  • Law Content Linting: should a paragraph be split into two, is it too complex by some language measure?
  • Law Style Linting: Proper line breaks in Markdown etc.

Having TravisCI test law change proposals would be mind-boggingly sweet.

@keilw
Copy link

keilw commented Aug 9, 2012

I'd say, a BDD style Functional Tests could be the only sensible way here.
"Given When Then..." is something you can clearly apply to laws, and Testing Frameworks like Concordion allow an executable (HTML or similar) document to run automatically. I guess if you apply this in a sensible way to Markdown, one should be able to track changes in the legal document, let's say the paragraph refers to a legal age of 21 years for some constraint and the law (text) is changed to 18 or another value, the test would fail;-)
JBehave is another option, there are a few, most of them use Java for the underlying DSL or execution layer, but there should proper BDD frameworks in other languages, e.g. Lettuce, the Python answer to Cucumber.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants