Skip to content

Test annotation tests automation #769

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

Closed

Conversation

jdesrosiers
Copy link
Member

No description provided.

@jdesrosiers jdesrosiers requested a review from a team as a code owner April 8, 2025 03:33
@jdesrosiers jdesrosiers force-pushed the annotation-tests branch 2 times, most recently from 0aa5d6d to 222eb12 Compare April 8, 2025 03:37
@jdesrosiers jdesrosiers closed this Apr 8, 2025
@jdesrosiers
Copy link
Member Author

Sorry. Thought I was testing this on my fork. Actual PR coming soon.

Copy link
Member

@gregsdennis gregsdennis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had a look through the first few, but haven't done a deep dive. Probably would be good to set this up with my implementation and run it.

"instance": {},
"assertions": [
{
"location": "/foo",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What location does this represent? I assume the instance, but there's schema location. There's also evaluation path that we could consider. I'm not sure evaluation path is necessary, but the other two should both be present, I think.

Secondly, it's inconsistent. Some are uri-encoded, and others aren't.

"expected": []
},
{
"location": "/3",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this location included? The instance location doesn't exist.

@jdesrosiers
Copy link
Member Author

@gregsdennis Thanks for the quick review, but it will be easier to wait until I make a proper PR. I had meant to create this on my fork for the purpose of testing the github action, but I was tired and accidentally created it here instead. The actual intended PR is coming soon.

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.

2 participants