Skip to content

ci: added additional test cases for convergence

shivani karipe requested to merge cherry-pick-757 into azure/m16-master

Type of change

  • Bug Fix
  • Feature
  • Pipeline
  • [* ] Test
  • Documentation

Does this introduce a change in the core logic?

  • [* ] No
  • Yes

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Anthos
  • [ *] Azure
  • GCP
  • IBM

Does this follow conventional commits spec?

  • No
  • [ *] Yes

Have you set the target Milestone?

  • No
  • [* ] Yes

Have you set the no-detached-pipeline label?

  • No
  • [ *] Yes

Updates description?

Update this part with a description of your changes

This MR introduces the following new test cases to improve the testing scenarios:

  • GENERAL READINESS: Check Seismic store service readiness -> This test case checks the readiness of the Seismic store service by using the svcstatus/readiness endpoint.
  • TENANT POST: Register a seismic-dms tenant -> This test case registers a seismic-dms tenant. If the tenant is not already present, it registers the tenant. The test case verifies the response codes and expects either a 201 or a 409.
  • DATASET REGISTER RANDOM: Register a new dataset with random name -> This test case registers a new dataset with a random name. It creates the dataset with a random name in the absolute path. Existing test cases currently create datasets in a specific path using the ?path option.
  • DATASET DELETE RANDOM: Delete random dataset -> It deletes the dataset that was created in the previous test case.
  • UTILITY LS SUBPROJECT : Retrieve list of datasets for a subproject -> It lists the datasets in the sub-project using the sd util.
  • Additionally, we have included an additional folder named initial setup containing the following test cases, which will perform the specified actions. These test cases are specifically added to facilitate the greenfield deployment instance. In a greenfield deployment instance, unlike the current OSDU instance, the legal tags might not be pre-existing, and the user might not be part of the datalake admin group. It is important to note that these test cases will only be executed for Azure, as they require the passing of additional parameters to be executed.
  • LEGAL GET: Get a Legal tag 01-> This test case verifies the presence of the legaltag01. If the tag is already present, it will skip the subsequent POST request to create the tag.
  • LEGAL POST: create Legal tag 01-> This test case will create the legaltag01 in-case its not already present
  • LEGAL GET: Get a Legal tag 02-> This test case verifies the presence of the legaltag02. If the tag is already present, it will skip the subsequent POST request to create the tag.
  • LEGAL POST: create Legal tag 02-> This test case will create the legaltag02 in-case its not already present
  • ENTITLEMENTS POST: add user to datalake admin group-> if the user is not already present in the users.datalake.admins group. it will add the user

Merge request reports