-
Notifications
You must be signed in to change notification settings - Fork 3
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
NameSpaceAdmin feature design and Runtime scenarios addition. #11
base: develop
Are you sure you want to change the base?
Conversation
Then Open and capture logs | ||
Then Verify the pipeline status is "Succeeded" | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed extra line spacing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok , Removed
ConnectionName=TestConnection | ||
projectId=cdf-athena | ||
dataset=test_automation | ||
#bqSourceTable=dummy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove the commented parameter values if not used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed .
projectId=cdf-athena | ||
dataset=test_automation | ||
#bqSourceTable=dummy | ||
#bqTargetTable=dummy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove the commented parameter values if not used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed
Feature: NameSpaceAdmin - Validate nameSpace admin design time scenarios | ||
|
||
@Namespaceadmin | ||
Scenario:Verify user is able to click the nameSpace admin tab and successfully navigates to the page |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verify user is able to click the nameSpace admin tab and successfully navigates to the page
to
Verify user is able to click on the name space admin tab and successfully navigates to the page
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed the Scenario Outline .
Then Click on NameSpace Admin link from the menu | ||
Then Click on create profile button for "default" Namespace | ||
Then Select a provisioner: "existingDataProc" for the compute profile | ||
Then Click on close button of compute profile properties page |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we not validating if we are able to successfully select the provisioner ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the validation steps .
Then Set nameSpace preferences with key: "keyValue" and value: "nameSpacePreferences2" | ||
Then Click on the Save & Close preferences button | ||
Then Click on edit namespace preferences to set namespace preferences | ||
Then Delete the preferences |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of calling this method 2 times to delete a namespace is it possible to create a step which accepts the name of namespaces as an argument and delete the namespaces by iterating on them ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes Vipin , This logic we will try to implement in Phase 3 developement .
Feature: NameSpaceAdmin - Validate nameSpace admin run time scenarios | ||
|
||
@BQ_SOURCE_TEST @BQ_SINK_TEST | ||
Scenario:To verify user should be able to run a pipeline successfully using the NameSpace preferences created |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To verify user should be able to run a pipeline successfully using the NameSpace preferences created
to
To verify if user is able to run a pipeline successfully using the name space preferences
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed the Scenario Outline .
Then Enter input plugin property: "table" with value: "bqSourceTable" | ||
Then Validate "BigQuery" plugin properties | ||
Then Close the Plugin Properties page | ||
Then Save the pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also add Preview steps before deploying..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have not added the preview steps because we just try to execute the pipline by creating the preferences inside any of the system/namespace level admin module . The verification is to use the created preferences /connections inside properties of source/sink and see a pipline run successfully .
Then Verify the pipeline status is "Succeeded" | ||
|
||
@BQ_SOURCE_TEST @BQ_SINK_TEST | ||
Scenario: To verify User should be able to create a test connection inside Namespace admin and use it in any of the selected plugin Property. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To verify User should be able to create a test connection inside Namespace admin and use it in any of the selected plugin Property.
To
To verify if user is able to create a connection from namespace admin and configure it for required plugins
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed the Scenario Outline .
Then Enter input plugin property: "table" with value: "bqTargetTable" | ||
Then Click plugin property: "truncateTable" | ||
Then Validate "BigQuery" plugin properties | ||
Then Close the Plugin Properties page |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add the preview steps here as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have not added the preview steps because we just try to execute the pipline by creating the preferences inside any of the system/namespace level admin module . The verification is to use the created preferences /connections inside properties of source/sink and see a pipline run successfully .
d3d9754
to
b52d09c
Compare
b52d09c
to
2e56d59
Compare
2e56d59
to
6105812
Compare
New features were added for Runtime and Design time for NameSpace admin Module