-
Notifications
You must be signed in to change notification settings - Fork 0
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
Automatic profile test #171
Comments
After an approbation of @FabienGandon , a first version of the script is published on the branch test-workflow |
Excellent. Thanks Nico ! Can I create a test-scenario branch to commit my work?
It could be useful to add some "Common sense" tests, what other examples than below can you imagine e.g. :
For meta.ttl, if we continue to work on this ontology, it could be benefit to add warning messages like :
It is just naive ideas. |
I just commited to add the asked features I pushed an example of what a report looks like (for now, WIP), and also added some mistakes in the ontology ON PURPOSE (you are all doing your job so well that I have to add errors myself)
|
I just also added a best practices check on ontology terms based on levenshtein distance |
The last heartbeat meeting showed the following points:
|
This bug was not a bug. The property hosts and isHostedOn still have respectedly a range and a domain set to hmas:Hostable To make it more clear, I changed a little bit the request and message error to detect more easily this case in the report: |
More recent news:
|
@NicoRobertIn : I believe that following the last heartbeat meeting we agreed to merge the script branch with the master and we could close that issue and copy some of its content to the documentation where needed. |
Just for the other ones who were not there at the heartbeat meeting, I made a markdown export of the test report that can be seen there: https://github.com/HyperAgents/hmas/blob/test-workflow/.acimov/output/actions.md I am currently making it compatible with pre-commit and eventually would like to finish this before the plenary meeting |
These last 2 days I extended a script @DrLeturc made to check the health of the ontology.
It uses the Corese python library with py4j.
My questions
Keep in mind: this is WIP, especially the format (issues will be posted in Corese repository to have some structured error reports)
What the script does
Here is a small portion of the output, given the project state 2 days ago:
The text was updated successfully, but these errors were encountered: