Skip to content
This repository has been archived by the owner on Nov 13, 2024. It is now read-only.

Test comment PR #37

Open
wants to merge 37 commits into
base: master
Choose a base branch
from
Open

Test comment PR #37

wants to merge 37 commits into from

Conversation

andriikorotkov
Copy link
Contributor

No description provided.

@andriikorotkov

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@andriikorotkov

This comment was marked as outdated.

@andriikorotkov

This comment was marked as outdated.

@andriikorotkov

This comment was marked as outdated.

@DoNotPanicUA DoNotPanicUA changed the title Update run-slash-commands.yml Test comment PR Sep 19, 2022
@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@andriikorotkov

This comment was marked as outdated.

@andriikorotkov

This comment was marked as outdated.

@andriikorotkov

This comment was marked as outdated.

@andriikorotkov

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA

This comment was marked as outdated.

@DoNotPanicUA
Copy link
Contributor

DoNotPanicUA commented Sep 29, 2022

/list-scenarios

https://github.com/airbytehq/airbyte-e2e-testing-tool/actions/runs/3152446801

Call help examples :

  • Get short help : /help name="<scenario_name>"
  • Get full help : /help-full name="<scenario_name>"

Scenario validation sings :

  • ✔️ - the scenario is valid and ready for use.
  • ❌ - the scenario is invalid. You can get a list of errors by a help command.

Available scenarios :

  • Custom connection sync scenario ✔️
    ℹ️ Configure custom connection using source settings and sync it.
  • Simple sync scenario ✔️
    ℹ️ Sync default connection.
  • Test invalid scenario ❌
    ℹ️ The scenario contains logical gap for the demo purposes
  • Update destination version scenario ✔️
    ℹ️ Configure default connection, set destination version. After sync, update version and repeat sync
  • Update source version scenario ✔️
    ℹ️ Configure default connection, set source version. After sync, update version and repeat sync

@DoNotPanicUA
Copy link
Contributor

DoNotPanicUA commented Sep 29, 2022

/help-full name="Update destination version scenario"

https://github.com/airbytehq/airbyte-e2e-testing-tool/actions/runs/3152482788

Scenario Update destination version scenario. ✔️

ℹ️ Configure default connection, set destination version. After sync, update version and repeat sync

Call examples :

  • Run scenario : /run-scenario name="Update destination version scenario" airbyte_1=<put_credential_name> source_1=<put_credential_name> destination_1=<put_credential_name> old_version=<parameter_value> new_version=<parameter_value>
  • Run scenario with local creds : /run-scenario-local name="Update destination version scenario" airbyte_1=<put_credential_name> source_1=<put_credential_name> destination_1=<put_credential_name> old_version=<parameter_value> new_version=<parameter_value>
    Note! The local scenario run requires file names in the folder secrets\. For example, some_cred_1=local_file.json
  • Get short help : /help name="Update destination version scenario"

Instances in the scenario

  • name : airbyte_1
    type : AIRBYTE
    credentials : airbyte_creds

  • name : source_1
    type : SOURCE
    credentials : source_creds

  • name : destination_1
    type : DESTINATION
    credentials : destination_creds

  • name : connection_1
    type : CONNECTION

Parameters in the scenario

  • name : old_version
    type : destination_version

  • name : new_version
    type : destination_version

Scenario actions

Preparation actions :
  • action : CONNECT_AIRBYTE_API
    resultInstance : airbyte_1

  • action : CREATE_SOURCE
    requiredInstances : [airbyte_1]
    resultInstance : source_1

  • action : CREATE_DESTINATION
    requiredInstances : [airbyte_1]
    resultInstance : destination_1

  • action : READ_DESTINATION_VERSION
    requiredInstances : [destination_1]

  • action : UPDATE_DESTINATION_VERSION
    requiredInstances : [destination_1]
    requiredParameters : [old_version]

  • action : CREATE_CONNECTION
    requiredInstances : [source_1, destination_1]
    resultInstance : connection_1

Scenario actions :
  • action : SYNC_CONNECTION
    requiredInstances : [connection_1]

  • action : UPDATE_DESTINATION_VERSION
    requiredInstances : [destination_1]
    requiredParameters : [new_version]

  • action : SYNC_CONNECTION
    requiredInstances : [connection_1]

  • action : UPDATE_DESTINATION_VERSION
    requiredInstances : [destination_1]
    requiredParameters : [before_test_version]

@DoNotPanicUA
Copy link
Contributor

DoNotPanicUA commented Sep 29, 2022

/help name="Test invalid scenario"

https://github.com/airbytehq/airbyte-e2e-testing-tool/actions/runs/3152484216

Scenario Test invalid scenario. ❌

ℹ️ The scenario contains logical gap for the demo purposes

⚠️ Failed validations :

Validation Result
Check that all instances have initialization action Instance(s) that should be initialized by an action : airbyte_1
Check that all action instances listed in the UsedInstances section Instance(s) used in the scenario actions but not described in the UsedInstances : airbyte_2
Action should have all mandatory attributes The action CONNECT_AIRBYTE_API should have result instance : [AIRBYTE] but have : []

Call examples :

  • Run scenario : /run-scenario name="Test invalid scenario" airbyte_1=<put_credential_name> source_1=<put_credential_name> destination_1=<put_credential_name> new_version=<parameter_value> old_version=<parameter_value>
  • Run scenario with local creds : /run-scenario-local name="Test invalid scenario" airbyte_1=<put_credential_name> source_1=<put_credential_name> destination_1=<put_credential_name> new_version=<parameter_value> old_version=<parameter_value>
    Note! The local scenario run requires file names in the folder secrets\. For example, some_cred_1=local_file.json
  • Get full help : /help-full name="Test invalid scenario"

Instances in the scenario

  • name : airbyte_1
    type : AIRBYTE
    credentials : airbyte_creds

  • name : source_1
    type : SOURCE
    credentials : source_creds

  • name : destination_1
    type : DESTINATION
    credentials : destination_creds

  • name : connection_1
    type : CONNECTION

Parameters in the scenario

  • name : new_version
    type : source_version

  • name : old_version
    type : source_version

@DoNotPanicUA
Copy link
Contributor

DoNotPanicUA commented Sep 29, 2022

/run-scenario name="Update destination version scenario" airbyte_1=tt_airbyte_dev2 source_1=tt_postgres_source_aws_1 destination_1=tt_postgres_destination_aws_1 old_version="0.3.22" new_version="0.3.23"

https://github.com/airbytehq/airbyte-e2e-testing-tool/actions/runs/3152605577

✔️ Scenario Update destination version scenario execution is finished successfully.

Preparation actions :

Preparation action Result Context Duration
Connect to Airbyte API 🟢 Instance name : airbyte_1. Url : https://dev2.airbyte.ga:80 0 sec
Create Source 🟢 Source name : source_1 1 sec
Create Destination 🟢 Destination name : destination_1 0 sec
Read destination version 🟢 Destination version 0.3.22 -> before_test_version 0 sec
Update Destination version 🟢 Destination version 0.3.22 -> old_version 0 sec
Create Connection 🟢 Connection name : connection_1 3 sec

Scenario actions :

Scenario action Result Context Duration
Sync Connection 🟢 Connection name : connection_1 22 sec
Update Destination version 🟢 Destination version 0.3.23 -> new_version 3 sec
Sync Connection 🟢 Connection name : connection_1 22 sec
Update Destination version 🟢 Destination version 0.3.22 -> before_test_version 2 sec

@mkhokh-33
Copy link
Contributor

/publish

@mkhokh-33
Copy link
Contributor

/publish

1 similar comment
@mkhokh-33
Copy link
Contributor

/publish

@andriikorotkov
Copy link
Contributor Author

andriikorotkov commented Oct 7, 2022

/run-scenario name="Update destination version scenario" airbyte_1=tt_airbyte_dev2 source_1=tt_postgres_source_aws_1 destination_1=tt_postgres_destination_aws_1 old_version="0.3.22" new_version="0.3.23"

https://github.com/airbytehq/airbyte-e2e-testing-tool/actions/runs/3204402871

✔️ Scenario Update destination version scenario execution is finished successfully.

Preparation actions :

Preparation action Result Context Duration
Connect to Airbyte API 🟢 Instance name : airbyte_1. Url : https://dev2.airbyte.ga:80 0 sec
Create Source 🟢 Source name : source_1 2 sec
Create Destination 🟢 Destination name : destination_1 0 sec
Read destination version 🟢 Destination version 0.3.22 -> before_test_version 0 sec
Update Destination version 🟢 Destination version 0.3.22 -> old_version 0 sec
Create Connection 🟢 Connection name : connection_1 4 sec

Scenario actions :

Scenario action Result Context Duration
Sync Connection 🟢 Connection name : connection_1 25 sec
Update Destination version 🟢 Destination version 0.3.23 -> new_version 1 sec
Sync Connection 🟢 Connection name : connection_1 22 sec
Update Destination version 🟢 Destination version 0.3.22 -> before_test_version 2 sec

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

Successfully merging this pull request may close these issues.

3 participants