-
-
Notifications
You must be signed in to change notification settings - Fork 6
Fix ids #1152
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
base: develop
Are you sure you want to change the base?
Conversation
Signed-off-by: Maciej Pijanowski <[email protected]>
|
@philipanda I went ahead with changing the regexp, but then I realized this check applies to checking IDs in .robot files, not in .json. Do we check .json somewhere as well? |
|
The reason for this change was an error when trying to sync the DB: |
|
Why does the regex need to be changed? Extracting the ID should work fine as we are taking the first group not the whole match. |
|
I don't think the IDs in test_cases.json are verified on their own. We assumed that by checking if the IDs in .robot are correct, and then checking if they match the ones in .json, by a transitive relation the IDs in .json will be correct as well. We are ignoring the .robot==.json check for now as they are not in sync and the effort to sync everything up was not done yet, so maybe that's why some errors got there |
It does not, I can drop this commit. Initially I thought it was used to validate
Thanks for confirmation. A simple check of ID field format in .json could also help here. |
As a temporary patch, yes, I agree. The time when the .robot files would get in sync with the .json is being postponed more than we initially thought. Eventually such test won't be needed though. |
No description provided.