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

[8.14 QA] Validate GraphQL Connector #2450

Open
19 of 24 tasks
kajal-elastic opened this issue Apr 25, 2024 · 1 comment
Open
19 of 24 tasks

[8.14 QA] Validate GraphQL Connector #2450

kajal-elastic opened this issue Apr 25, 2024 · 1 comment
Assignees

Comments

@kajal-elastic
Copy link

kajal-elastic commented Apr 25, 2024

Non-regression QA

  • GraphQL

Note: always test with the latest Build Candidate on Elastic Cloud, using the full Elastic stack

  • Start the whole stack from scratch and navigate to Enterprise Search
  • Check that no indices are shown in the top level Indices list
  • Click on "Create an Elasticsearch index" - a new page is open where you can select an ingestion method
  • Choose Connector -> Use a connector
  • Choose the connector you want to test and Continue
  • Create an index with a valid name and Universal language

  • Connector name and description are editable on the Configurations page

  • Connector can be deleted from the Indices page

  • Connector can be deleted from the Indices page and it can be recreated with the same name after

  • Pull connectors repository, run make install but do not run connector yet

  • Verify that you are redirected to "configuration" page where you can create an api key and can copy connector id / whole section of config into the connector

  • Update connector configuration with the api_key and connector_id, plus choose a service_type to test and set it in config

  • Start the connector by running make run - verify that it starts and does not actually do anything yet

  • Wait for the Kibana page with the connector configuration to update and verify that it's possible to edit connector configuration now

  • Edit and save connector configuration, then reload the page and verify that configuration is properly saved

  • Click on "Set schedule and sync" and verify that you're redirected to the scheduling tab

  • Enable scheduling for frequency = every minute and save schedule; refresh the page and verify that the changes were stored

  • Switch to the connector and wait for a minute or two, verify that connector starts to ingest data

  • Verify that the data from the connector appears in the expected index

  • Verify that on the index list page index information is updated properly, showing expected number of documents and new index size

  • Verify that on the connector overview page "Document Count" is updated to reflect the number of documents in the index

  • Verify that you can see ingested documents in documents tab

  • Verify that index mappings are correct on the index mappings tab

Record a short demo showing the connectors' configuration and that there were documents ingested

@kajal-elastic
Copy link
Author

@danajuratoni @DianaJourdan I have validated the GraphQL connector and recorded the demo & uploaded on drive:

GraphQL

Updated steps as per the newer Elasticsearch versions

  1. For--> Click on "Create an Elasticsearch index" - a new page is open where you can select an ingestion method --> Click on Create a Connector - a new page is open where you can find the Connectors tile

  2. For -->Connector can be deleted from the Indices page --> Connector can be deleted from the Connectors page

  3. For --> Connector can be deleted from the Indices page and it can be recreated with the same name after --> Connector can be deleted from the Connectors page along with its index and it can be recreated with the same name after

  4. For --> Enable scheduling for frequency = every minute and save schedule; refresh the page and verify that the changes were stored --> Setting the Scheduling with frequency= every 5 minutes is there so we have checked it for every 5 minutes and specific minute in every hour..

  5. For --> Verify that on the index list page index information is updated properly, showing the expected number of documents and new index size --> The Index size is not displayed on the Elasticsearch Indices page. We are able to check the same from Index Management Page as it is displayed there.

Please review the same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants