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

Fix some tests (#850) #869

Merged
merged 1 commit into from
Jan 29, 2024
Merged

Conversation

JPryce-Aklundh
Copy link
Contributor

  • A setup block was (silently) failing due to an extra trailing comma. With that fixed, the test for the other example failed because Charlie was not reported as a string in the asciidoc.
  • test-result-skip is not needed when a result is missing, only when a result is present but different from what the tester would get.
  • No need to test-skip when query parameters are missing: the tester skips automatically.
  • After a query block, there may only be one result block, either of type queryresult or queryplan. If there's both of them, the parser will pick the first one, but its internal state will probably also get messed up.
  • The last two query plans were surely wrong (they didn't have the right return value), while I'm not sure about the first. It may be something that changed in newer releases or IDK, they look pretty similar.

- A setup block was (silently) failing due to an extra trailing comma.
With that fixed, the test for the other example failed because `Charlie`
was not reported as a string in the asciidoc.
- `test-result-skip` is not needed when a result is missing, only when a
result is present but _different_ from what the tester would get.
- No need to `test-skip` when query parameters are missing: the tester
skips automatically.
- After a query block, there may only be _one_ result block, either of
type `queryresult` or `queryplan`. If there's both of them, the parser
will pick the first one, but its internal state will probably also get
messed up.
- The last two query plans were surely wrong (they didn't have the right
return value), while I'm not sure about the first. It may be something
that changed in newer releases or IDK, they look pretty similar.

---------

Co-authored-by: Jens Pryce-Åklundh <[email protected]>
@JPryce-Aklundh JPryce-Aklundh added cherry-picked This PR was merged in another version and the changes has been cherry picked in this PR. 5.x Applies to all Neo4j 5 docs labels Jan 29, 2024
@JPryce-Aklundh JPryce-Aklundh merged commit f4e7ad7 into neo4j:5.x Jan 29, 2024
4 checks passed
@JPryce-Aklundh JPryce-Aklundh deleted the 5.x-cherry-pick-850 branch January 29, 2024 10:15
@neo-technology-commit-status-publisher
Copy link
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-cypher-869.surge.sh

Updated pages:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5.x Applies to all Neo4j 5 docs cherry-picked This PR was merged in another version and the changes has been cherry picked in this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants