-
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
Controlcenter e2e 2 #13
base: develop
Are you sure you want to change the base?
Conversation
ff32a34
to
7928b3a
Compare
|
||
@Controlcenter | ||
|
||
Feature: Controlcenter - Validate control center page flow |
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 change the feature title after segregating the tests for design and run-time feature
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 feature title for design and run-time feature
Then Verify the user is able to enter the value of the key in the value input field "value" | ||
Then Verify user is able to click on save and close button of set preferences | ||
Then Verify user is able to click on the data pipeline added in the control center page | ||
Then Run the Pipeline in Runtime |
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.
If we are setting the key and value for a particular macro property field of plugin then, we need to even check by running the pipeline whether the added preferences are used while 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 are already checking it by keeping projectids in source and sink plugin as macros.
Then Click on the Hamburger bar on the left panel | ||
Then Click on Control Center link from the hamburger menu | ||
Then Click on the delete icon of the dataset entity and the dataset should get deleted successfully | ||
Then Verify the deleted dataset "BQReferenceNameDataset" entity is not present in control center 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.
What is the dataset name we are searching for? What is the dataset name 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.
Changed the dataset name to the relevant one.
Then Verify the pipeline status is "Succeeded" | ||
Then Click on the Hamburger bar on the left panel | ||
Then Click on Control Center link from the hamburger menu | ||
Then Click on the truncate icon of the dataset entity and the dataset should get truncated successfully |
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.
How are we validating whether is truncate is successful or not? Add validation step
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.
Trncate cannot be validated as its showing only one green popup in the grid thats appears for few seconds and no such confirmation messages are coming for it
Then Verify the deleted dataset "BQReferenceNameDataset" entity is not present in control center page | ||
|
||
@BQ_INSERT_INT_SOURCE_TEST @BQ_SINK_TEST | ||
Scenario: Verify that User is able to perform Truncate operation on dataset entity successfully. |
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.
Try to club the above and this case, having truncate then validate and then delete dataset in single scenario.
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.
clubbed the two scenrios first truncate and then delete
Then Click on the view details tab of dataset entity page to see the details page of the dataset | ||
Then Verify user is successfully navigated to details page of the dataset entity | ||
Then Click on the back link of the view details page of dataset entity | ||
Then Click on the close link of the view details page of dataset entity to close the details 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 validation step to verify the details page is closed successfully
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 step that user is navigated back to the main control center page
Then Verify user is able to see all entities displayed message on the basis of filter selection | ||
|
||
@BQ_INSERT_INT_SOURCE_TEST @BQ_SINK_TEST | ||
Scenario: Verify User is able to switch between Schema and programs link of the dataset and can see the details of both successfully |
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.
Change to ----Verify the user is able to switch between schema and programs of dataset successfully
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.
done
# License for the specific language governing permissions and limitations under | ||
# the License. | ||
|
||
@Controlcenter |
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.
Segregate Runtime and design time features in sparate feature files . All scenarios should not be present in a Single file .
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.
done segregated the files
Then Verify the deleted pipeline is not present in the control center page | ||
|
||
@BQ_INSERT_INT_SOURCE_TEST @BQ_SINK_TEST | ||
Scenario: Verify User is able to create pipeline by using preferences,entering the key and value pair and validate it deploy successfully. |
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.
Change it to : Verify the user is able to set preferences for a deployed pipline and use the same while running the pipline .
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
Then Verify the user is able to set the preferences for the created pipeline in the control center page | ||
Then Verify the user is able to enter the value in the key input field "keyValue" | ||
Then Verify the user is able to enter the value of the key in the value input field "value" | ||
Then Verify user is able to click on save and close button of set 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.
Here we are only setting the preferences but not using the same while running the pipline . Once you set preferences they should be used in the pipline
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.
already added the macros for this
Then Verify user is able to click on the delete icon of preferences to delete the added preferences successfully | ||
|
||
@BQ_INSERT_INT_SOURCE_TEST @BQ_SINK_TEST | ||
Scenario: Verify that User is able to click on the dataset entity and User is navigated to the details page of the dataset successfully |
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.
Change it to : Verify that User is able to click on the dataset entity and navigated to the details page of the dataset successfully
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
Then Click on the Hamburger bar on the left panel | ||
Then Click on Control Center link from the hamburger menu | ||
Then Verify user is able to click on the dataset entity icon to see the details page of the dataset | ||
Then Verify user is navigated to the details page of the dataset entity icon successfully |
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.
What verification we are doing here to know that the user is succesfully redirected to details page of dataset ?
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.
user is navigated to the details page after clicking on details link
Then Click on the truncate icon of the dataset entity and the dataset should get truncated successfully | ||
|
||
@BQ_INSERT_INT_SOURCE_TEST @BQ_SINK_TEST | ||
Scenario:Verify that User clicks on Dataset and view details page should be dispalyed,is able to click on view details link and navigate back to main details page and then close it. |
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.
Rephrase it : Verify the user is able to navigate to and from details page of a dataset inside control center
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.
rephrased
Then Verify the pipeline status is "Succeeded" | ||
Then Click on the Hamburger bar on the left panel | ||
Then Click on Control Center link from the hamburger menu | ||
Then Verify user is able to see the display message on the basis of filter selection in control center 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.
what verification is this step doing ?
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 this step and added one step for all entities filter selection
Then Verify user is navigated to the programs details page of the dataset entity page | ||
|
||
@BQ_INSERT_INT_SOURCE_TEST @BQ_SINK_TEST | ||
Scenario: Verify User is able to sort the entities by A-Z,Z-A,Oldest and newest filters. |
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.
change it to 'Verify User is able to sort the entities with all the available filter types in control center'
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
Then Click on the close icon of the added tag and verify that the tag count decreases | ||
|
||
@BQ_INSERT_INT_SOURCE_TEST @BQ_SINK_TEST | ||
Scenario: Verify user should be able to search the data set using the tags and should be validated from displayed message. |
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.
Change it : Verify the user is able to search a dataset using the added tag
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.
remove space and write dataset , change it everyewhere
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.
done
Then Click on the plus add button of the dataset entity to add the tags successfully | ||
Then Verify user is able to enter the values in tag input field: "testingTag" | ||
Then Enter the text in search tab "testingTag" in control center | ||
Then Verify the searched tag appears successfully on the control center 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.
For every scenario we do not need to create , deploy and run a pipline . Either you can create a pipline and once it is saved in control center the necessary user actions can be covered over that pipline and related dataset .
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.
done
Then Click on the Hamburger bar on the left panel | ||
Then Click on Control Center link from the hamburger menu | ||
Then Click on the Plus Green Button to import the pipelines | ||
Then Verify user is able to click on the create button to create a pipeline successfully |
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.
Change -- 'Click on create button to create a pipeline'. Change in all scenarios wherever used.
b89220f
to
9fa8169
Compare
5e26a93
to
be2c4f9
Compare
No description provided.