-
Notifications
You must be signed in to change notification settings - Fork 1
Add CLI Tool and updated README for Concerto Conformance Suite #19
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
Conversation
README.md
Outdated
| The Concerto Conformance Test Suite provides a standardized, automated testing suite to validate models and semantic behavior across Accord Project Concerto implementations. | ||
| ## Overview | ||
| This repository includes: | ||
| 1. A curated set of semantic validation rules |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a "curated" sample? I think it's all the semantic rules we've discovered so far isn't it?
README.md
Outdated
| 3. Tests written using Cucumber, offering behavior-driven, human-readable test definitions | ||
| 4. Support for both JavaScript and C# environments | ||
| The suite specifically tests core components of the Concerto ecosystem: | ||
| 1. The Parser from `@accordproject/concerto-cto` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't specifically test the parser, that's more of a side effect.
| 2. Choose between JavaScript or C# environments | ||
| 3. Automatically generate test files with proper imports | ||
| 4. Run the relevant conformance tests seamlessly | ||
| ## Future Roadmap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you can add those to the project board. You don't need to add them here unless you don't have time to add these to the repository before GSoC finishes. But keeping them is fine as well. Just keep in mind to have them up to date.
…th for the parser, modelmanager and modelfile Signed-off-by: Anshukumar123975 <[email protected]>
Signed-off-by: Anshukumar123975 <[email protected]>
Co-authored-by: Ertugrul Karademir <[email protected]> Signed-off-by: Anshukumar123975 <[email protected]>
Co-authored-by: Ertugrul Karademir <[email protected]> Signed-off-by: Anshukumar123975 <[email protected]>
Co-authored-by: Ertugrul Karademir <[email protected]> Signed-off-by: Anshukumar123975 <[email protected]>
Co-authored-by: Ertugrul Karademir <[email protected]> Signed-off-by: Anshukumar123975 <[email protected]>
Signed-off-by: Anshukumar123975 <[email protected]>
Description:
This PR introduces:
Details about the CLI Tool:
Allows users to interactively specify custom source paths for:
Parser from
@accordproject/concerto-ctoModelFile from
@accordproject/concerto-coreModelManager from
@accordproject/concerto-core