Skip to content

dialogflow: delete samples that are not in docs #2602

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

Merged
merged 2 commits into from
Apr 10, 2020
Merged

Conversation

nnegrey
Copy link
Contributor

@nnegrey nnegrey commented Apr 8, 2020

fix the tests that are broken after the deletions
Update this PR: #2483

Fixes #2252

It's a good idea to open an issue first for discussion.

  • Tests pass
  • Appropriate changes to README are included in PR
  • API's need to be enabled to test (tell us)
  • Environment Variables need to be set (ask us to set them)

@nnegrey nnegrey self-assigned this Apr 8, 2020
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Apr 8, 2020
@nnegrey nnegrey changed the title dialogflow: delete samples that are not in docs and fix the tests tha… dialogflow: delete samples that are not in docs Apr 8, 2020
@nnegrey nnegrey removed their assignment Apr 9, 2020
@nnegrey nnegrey marked this pull request as ready for review April 9, 2020 20:37
@nnegrey nnegrey requested a review from a team April 9, 2020 20:37
Comment on lines 44 to 45
private static String TEST_KNOWLEDGE_BASE_ID = "MTA4MzE0ODY5NTczMTQzNzU2ODA";
private static String TEST_DOCUMENT_ID = "MTUwNjk0ODg1NTU4NzkzMDExMg";
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we be concerned about these constants and running testing jobs in parallel. (ie. j8 & j11)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Not for this one. I used to have these tests dynamically create these resources, but the API has to do some ML training for an indeterminate time on the created resources which would create a flaky test occasionally. There are some more involved work-arounds to get around this, but would significantly complicate the tests.

So instead having this resource be static and used for "prediction" should handle any number of parallel requests and all of them should get an identical response and only a change to the Document we created should break this.

Copy link
Contributor

@lesv lesv left a comment

Choose a reason for hiding this comment

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

Minor question - LGTM if you think it's ok.

@nnegrey nnegrey merged commit d1a38a3 into master Apr 10, 2020
@nnegrey nnegrey deleted the dialogflow-cleanup branch April 10, 2020 15:54
Shabirmean pushed a commit that referenced this pull request Nov 14, 2022
* dialogflow: delete samples that are not in docs and fix the tests that are broken after the deletions

* update README
Shabirmean pushed a commit that referenced this pull request Nov 15, 2022
* dialogflow: delete samples that are not in docs and fix the tests that are broken after the deletions

* update README
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update Dialogflow tests
3 participants