PromucFlow_constructor/app/client/cypress/e2e/GSheet/AllAccess_Spec.ts

360 lines
12 KiB
TypeScript
Raw Normal View History

test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
/// <reference types="Cypress" />
import { GSHEET_DATA } from "../../fixtures/test-data-gsheet";
import {
homePage,
gsheetHelper,
dataSources,
agHelper,
entityExplorer,
table,
assertHelper,
appSettings,
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
} from "../../support/Objects/ObjectsCore";
const workspaceName = "gsheet apps";
const dataSourceName = "gsheet-all";
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
let appName = "gsheet-app";
let spreadSheetName = "test-sheet";
fix: Remove Gsheets unauth method (#36125) ## Description This PR temporarily removes the unauthorised Google Sheets method to ensure users are only shown methods that would work and avoid causing confusion. - The feature flag wasn't used here as the form JSON config's method field does not support hidden fields using feature flag and we avoided writing a logic specifically to remove the field from JSON before sending it as once the other methods get authorised again, we won't need the feature flag again Fixes #35523 ## Automation /test gsheet ### :mag: Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!TIP] > 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/10789501829> > Commit: 040643a4d4ed4f2467a0af5733f4015a92d74e26 > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=10789501829&attempt=1" target="_blank">Cypress dashboard</a>. > Tags: `@tag.GSheet` > Spec: > <hr>Tue, 10 Sep 2024 09:37:24 UTC <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [x] No <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Simplified authorization options for Google Sheets integration, now limited to read and write access for selected sheets only. - **Bug Fixes** - Updated integration tests to reflect the removal of outdated Google Sheets permission options, ensuring tests align with current authorization constraints. - **Tests** - Temporarily skipped multiple test suites related to Google Sheets functionality to streamline testing and focus on relevant tests. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2024-09-10 11:51:50 +00:00
describe.skip(
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
"GSheet-Functional Tests With All Access",
{
tags: ["@tag.Datasource", "@tag.GSheet", "@tag.Git", "@tag.AccessControl"],
},
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
function () {
before("Setup app and spreadsheet", function () {
//Add a new app and an add new spreadsheet query
//Setting up the spreadsheet name
const uuid = Cypress._.random(0, 10000);
spreadSheetName = spreadSheetName + "_" + uuid;
appName = appName + "-" + uuid;
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
//Adding query to insert a new spreadsheet
homePage.NavigateToHome();
homePage.SelectWorkspace(workspaceName);
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
homePage.CreateAppInWorkspace(workspaceName, appName);
gsheetHelper.AddNewSpreadsheetQuery(
dataSourceName,
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
spreadSheetName,
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
JSON.stringify([GSHEET_DATA[0]]),
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
);
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
cy.get("@postExecute").then((interception: any) => {
expect(
interception.response.body.data.body.properties.title,
).to.deep.equal(spreadSheetName);
});
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
it("1. Add and verify fetch details query", () => {
entityExplorer.CreateNewDsQuery(dataSourceName);
feat: Enable new toolbar for cypress (#37148) ## Description This PR enabled IDE toolbar for cypress. Fixes #37217 ## Automation /ok-to-test tags="@tag.All" ### :mag: Cypress test results <!-- This is an auto-generated comment: Cypress test results --> > [!TIP] > 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉 > Workflow run: <https://github.com/appsmithorg/appsmith/actions/runs/12115693818> > Commit: f2af8705e91af400b3a80f6684cce7fb487f1ca3 > <a href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=12115693818&attempt=2" target="_blank">Cypress dashboard</a>. > Tags: `@tag.All` > Spec: > <hr>Mon, 02 Dec 2024 12:19:38 UTC <!-- end of auto-generated comment: Cypress test results --> ## Communication Should the DevRel and Marketing teams inform users about this change? - [ ] Yes - [x] No <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced a new feature flag `release_actions_redesign_enabled` to enhance user experience. - **Bug Fixes** - Updated method calls in various test cases to improve consistency and reliability in interactions, specifically renaming methods related to data sources and queries. - Improved error handling and validation in tests for MongoDB query functionalities. - **Documentation** - Enhanced test coverage and assertions for various functionalities, including API actions, Google Sheets queries, and JavaScript function execution. - **Style** - Updated CSS selectors for improved consistency and maintainability across components and test cases. - **Tests** - Refactored multiple test cases to utilize new helper methods, improving code clarity and reducing direct DOM manipulation. - Enhanced visual tests for JSEditor and improved interaction with the run button. - Added new assertions and enhanced the structure of tests for various components, including API response handling and widget interactions. - Streamlined interaction with the settings toolbar in various test cases by encapsulating functionality within the `PluginActionForm` class. - Introduced new `data-testid` attributes across various components to enhance testability. - **Chores** - Removed unused imports and streamlined method calls for better performance and readability. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2024-12-03 03:51:43 +00:00
agHelper.RenameQuery("Fetch_Details");
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
dataSources.ValidateNSelectDropdown(
"Operation",
"Fetch Many",
"Fetch Details",
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
);
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
dataSources.ValidateNSelectDropdown("Entity", "Spreadsheet");
agHelper.Sleep(500);
dataSources.ValidateNSelectDropdown("Spreadsheet", "", spreadSheetName);
dataSources.RunQuery();
cy.get("@postExecute").then((interception: any) => {
expect(interception.response.body.data.body.name).to.deep.equal(
spreadSheetName,
);
});
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
it("2. Verify Insert one and Insert many queries", () => {
// add insert one query and verify
gsheetHelper.AddInsertOrUpdateQuery(
"Insert One",
dataSourceName,
spreadSheetName,
JSON.stringify(GSHEET_DATA[1]),
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
);
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
cy.get("@postExecute").then((interception: any) => {
expect(interception.response.body.data.body.message).to.deep.equal(
"Inserted row successfully!",
);
});
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
// add insert many query and verify
gsheetHelper.AddInsertOrUpdateQuery(
"Insert Many",
dataSourceName,
spreadSheetName,
JSON.stringify(GSHEET_DATA.slice(2, 10)),
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
);
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
cy.get("@postExecute").then((interception: any) => {
expect(interception.response.body.data.body.message).to.deep.equal(
"Inserted rows successfully!",
);
});
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
it("3. Verify Update one and Update many queries", () => {
// add update one query and verify
gsheetHelper.AddInsertOrUpdateQuery(
"Update One",
dataSourceName,
spreadSheetName,
JSON.stringify(GSHEET_DATA[1]),
);
cy.get("@postExecute").then((interception: any) => {
expect(interception.response.body.data.body.message).to.deep.equal(
"Updated sheet successfully!",
);
});
// add update many query and verify
gsheetHelper.AddInsertOrUpdateQuery(
"Update Many",
dataSourceName,
spreadSheetName,
JSON.stringify(GSHEET_DATA.slice(2, 4)),
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
);
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
cy.get("@postExecute").then((interception: any) => {
expect(interception.response.body.data.body.message).to.deep.equal(
"Updated sheet successfully!",
);
});
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
it("4. Verify Fetch many query", () => {
// Add simple Fetch many query and verify
gsheetHelper.EnterBasicQueryValues(
"Fetch Many",
dataSourceName,
spreadSheetName,
);
dataSources.RunQueryNVerifyResponseViews(GSHEET_DATA.length);
dataSources.AssertQueryTableResponse(0, GSHEET_DATA[0].uniq_id);
dataSources.AssertQueryTableResponse(1, "ホーンビィ 2014 カタログ"); // Asserting other language
dataSources.AssertQueryTableResponse(2, "₹, $, €, ¥, £"); // Asserting different symbols
dataSources.AssertQueryTableResponse(3, "!@#$%^&*"); // Asserting special chars
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
// Update query to fetch only 1 column and verify
gsheetHelper.SelectMultiDropDownValue("Columns", "product_name");
dataSources.RunQuery();
dataSources.RunQueryNVerifyResponseViews(GSHEET_DATA.length);
dataSources.AssertQueryTableResponse(0, GSHEET_DATA[0].product_name);
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
//Remove column filter and add Sort By Ascending and verify
gsheetHelper.SelectMultiDropDownValue("Columns", "product_name"); //unselect the Columns dd value
agHelper.EnterValue("price", {
propFieldName: "",
directInput: false,
inputFieldName: "Sort By",
});
dataSources.RunQueryNVerifyResponseViews(GSHEET_DATA.length);
dataSources.AssertQueryTableResponse(
0,
"5afbaf65680c9f378af5b3a3ae22427e",
);
dataSources.AssertQueryTableResponse(
1,
"ラーニング カーブ チャギントン インタラクティブ チャッツワース",
); // Asserting other language
dataSources.AssertQueryTableResponse(2, "₹, $, €, ¥, £"); // Asserting different symbols
dataSources.AssertQueryTableResponse(3, "!@#$%^&*"); // Asserting special chars
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
// Sort by descending and verify
dataSources.ClearSortByOption(); //clearing previous sort option
dataSources.EnterSortByValues("price", "Descending");
dataSources.RunQuery();
dataSources.RunQueryNVerifyResponseViews(GSHEET_DATA.length);
dataSources.AssertQueryTableResponse(
1,
"ホーンビー ゲージ ウェスタン エクスプレス デジタル トレイン セット (eLink および TTS ロコ トレイン セット付き)",
); // Asserting other language
dataSources.AssertQueryTableResponse(
4,
"Hornby Gauge Western Express Digital Train Set with eLink and TTS Loco Train Set",
);
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
// Filter by where clause and verify
agHelper.TypeDynamicInputValueNValidate(
"price",
dataSources._nestedWhereClauseKey(0),
);
agHelper.TypeDynamicInputValueNValidate(
"100",
dataSources._nestedWhereClauseValue(0),
);
dataSources.RunQuery();
dataSources.RunQueryNVerifyResponseViews(8);
dataSources.AssertQueryTableResponse(
0,
"87bbb472ef9d90dcef140a551665c929",
);
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
// Filter by cell range and verify
dataSources.ValidateNSelectDropdown(
"Filter Format",
"Where Clause",
"Cell range",
);
agHelper.EnterValue("A2:A5", {
propFieldName: "",
directInput: false,
inputFieldName: "Cell range",
});
dataSources.RunQuery();
dataSources.RunQueryNVerifyResponseViews(4);
dataSources.AssertQueryTableResponse(
0,
"eac7efa5dbd3d667f26eb3d3ab504464",
);
fix: gsheet cell range filter format issue fixed (#26827) ## Description This PR fixes the issue with filter format in gsheet query creation: The issue occurs when say the spreadsheet has data in the following format: <img width="258" alt="Screenshot 2023-08-31 at 3 09 03 PM" src="https://github.com/appsmithorg/appsmith/assets/30018882/88f8fdae-4223-468a-b05d-04fd8e9841dc"> Now if we write a query with where clause to to fetch all records with Id < 3, it returns first two records as expected. Now if we change the filter format to cell range and define cell range as b2:b4, It should return `Name: test1 test2 test3`, but instead it throws error, because it first filters out data based on cell range provided, and post that it checks if the where conditions are defined in actionConfig and applies that on the result set to filter data. In above example result set would be `Name: test1 test2 test3` and it tries to apply the where clause condition of `Id < 2` In order to solve the issue, we need to apply where conditions only when filter format is `Where Clause`. #### PR fixes following issue(s) Fixes #25447 > if no issue exists, please create an issue and ask the maintainers about this first > > #### Media > A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video > > #### Type of change - Bug fix (non-breaking change which fixes an issue) > > > ## Testing > #### How Has This Been Tested? > Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration. > Delete anything that is not relevant - [x] Manual - [ ] JUnit - [ ] Jest - [x] Cypress > > #### Test Plan > Add Testsmith test cases links that relate to this PR > > #### Issues raised during DP testing > Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR) > > > ## Checklist: #### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [x] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [x] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [x] Test plan has been peer reviewed by project stakeholders and other QA members - [x] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed Co-authored-by: “sneha122” <“sneha@appsmith.com”>
2023-09-01 13:20:21 +00:00
});
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
it("5. Update a record which is not present and verify the error", () => {
//preparing data
let data = GSHEET_DATA[1];
data.rowIndex = "15";
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
// add update one query and verify
gsheetHelper.EnterBasicQueryValues(
"Update One",
dataSourceName,
spreadSheetName,
false,
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
);
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
agHelper.EnterValue(JSON.stringify(data), {
propFieldName: "",
directInput: false,
inputFieldName: "Update row object",
});
dataSources.RunQuery({
expectedStatus: false,
});
cy.get("@postExecute").then((interception: any) => {
expect(interception.response.body.data.body).to.deep.equal(
"No data found at this row index.",
);
});
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
it("6. Convert field to JS and verify", () => {
// Switch js on sheet name then run query and verify
gsheetHelper.EnterBasicQueryValues(
"Fetch Many",
dataSourceName,
spreadSheetName,
false,
);
agHelper.GetNClick(
dataSources._getJSONswitchLocator("Sheet name"),
0,
true,
);
dataSources.RunQueryNVerifyResponseViews(10);
dataSources.AssertQueryTableResponse(
0,
"eac7efa5dbd3d667f26eb3d3ab504464",
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
);
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
//Enter a wrong sheet name then run query and verify
agHelper.EnterValue("Sheet 2", {
propFieldName: "",
directInput: false,
inputFieldName: "Sheet name",
});
dataSources.RunQuery({
expectedStatus: false,
});
cy.get("@postExecute").then((interception: any) => {
expect(interception.response.body.data.body).to.deep.equal(
"Unable to parse range: 'Sheet 2'!1:1",
);
});
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
//Covert sheet name field to dropdown then run query and verify
agHelper.HoverElement(dataSources._getJSONswitchLocator("Sheet name"));
agHelper.AssertTooltip("Clear the field to toggle back");
agHelper.EnterValue("", {
propFieldName: "",
directInput: false,
inputFieldName: "Sheet name",
}); //Clearing the sheet name field
agHelper.GetNClick(
dataSources._getJSONswitchLocator("Sheet name"),
0,
true,
); // Converting the field to dropdown
dataSources.ValidateNSelectDropdown("Sheet name", "", "Sheet1");
dataSources.RunQueryNVerifyResponseViews(10);
dataSources.AssertQueryTableResponse(
0,
"eac7efa5dbd3d667f26eb3d3ab504464",
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
);
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
it("7. Verify Delete query", function () {
// Delete spreadsheet and app
gsheetHelper.EnterBasicQueryValues(
"Delete One",
dataSourceName,
spreadSheetName,
);
agHelper.EnterValue(GSHEET_DATA[0].rowIndex, {
propFieldName: "",
directInput: false,
inputFieldName: "Row Index",
});
dataSources.RunQuery();
cy.get("@postExecute").then((interception: any) => {
expect(interception.response.body.data.body.message).to.deep.equal(
"Deleted row successfully!",
);
});
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
it("8. Import an app with all access sheet", function () {
homePage.NavigateToHome();
homePage.ImportApp("ImportAppAllAccess.json", workspaceName);
assertHelper.WaitForNetworkCall("importNewApplication").then(() => {
agHelper.Sleep();
//Validate table is not empty!
table.WaitUntilTableLoad(0, 0, "v2");
});
// Assert table data
table.ReadTableRowColumnData(0, 0, "v2").then((cellData) => {
expect(cellData).to.eq("eac7efa5dbd3d667f26eb3d3ab504464");
});
homePage.NavigateToHome();
homePage.DeleteApplication("ImportAppAllAccess");
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
it("9. App level import of app with all access gsheet", function () {
homePage.CreateAppInWorkspace(workspaceName, "AppLevelImport");
appSettings.OpenAppSettings();
appSettings.GoToImport();
agHelper.ClickButton("Import");
homePage.ImportApp("ImportAppAllAccess.json", "", true);
cy.wait("@importNewApplication").then(() => {
agHelper.Sleep();
agHelper.RefreshPage();
table.WaitUntilTableLoad(0, 0, "v2");
});
// Assert table data
table.ReadTableRowColumnData(0, 0, "v2").then((cellData) => {
expect(cellData).to.eq("eac7efa5dbd3d667f26eb3d3ab504464");
});
homePage.NavigateToHome();
homePage.DeleteApplication("AppLevelImport");
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
after("Delete spreadsheet and app", function () {
// Delete spreadsheet and app
homePage.EditAppFromAppHover(appName);
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
gsheetHelper.DeleteSpreadsheetQuery(dataSourceName, spreadSheetName);
cy.get("@postExecute").then((interception: any) => {
expect(interception.response.body.data.body.message).to.deep.equal(
"Deleted spreadsheet successfully!",
);
});
homePage.NavigateToHome();
homePage.DeleteApplication(appName);
test: Gsheet Automation (#25255) ## Description - Automated below queries for gsheet 1. Fetch Details 2. Insert one 3. Insert many 4. Update one 5. Update many 6. Fetch many 7. Delete One - Added workflow to schedule run for gsheet automated tests on the hosted instance - Added a new cypress config file which will be used to run the gsheet tests - Added tests for folowing permission/scope options `All access`, `selected access`, `Read/write | All google sheets` and `Read | All google sheets` - Added negative scenarios - Added tests to verify widget binding for both suggested widget and drag n drop widget for both selected and all access permission/scope #### Type of change - Cypress ## Testing > #### How Has This Been Tested? - [x] Cypress > > ## Checklist: #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed
2023-07-26 13:26:24 +00:00
});
test: Cypress - Added Tags to test cases - @tag.GSheet, @tag.Datasource, @tag.JS, @tag.IDE, @tag.Settings, @tag.Binding (#29471) ## Description > Adding tags to the existing test cases Run GSheet test cases - `/ok-to-test tags="@tag.GSheet"` Run JS test cases - ` /ok-to-test tags="@tag.JS"` Run IDE test cases - ` /ok-to-test tags="@tag.IDE"` Run Binding test cases - ` /ok-to-test tags="@tag.Binding"` Few datasource testcases (tags are added to few) using - ` /ok-to-test tags="@tag.Datasource"` To run both GSheet and Datasource tagged testcases -` /ok-to-test tags="@tag.Datasource,@tag.GSheet"` To run both Binding and IDE tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE"` To run both Binding, IDE, JS tagged testcases - ` /ok-to-test tags="@tag.Binding,@tag.IDE,@tag.JS"` #### Type of change - Chore (housekeeping or task changes that don't impact user perception) ## Testing #### How Has This Been Tested? - [x] Manual - [x] Cypress #### Test Plan > ok to test with tags added ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced test suite categorization with the addition of metadata tags for improved filtering and organization. - **Refactor** - Reorganized test suite structures for clarity and maintainability. - Updated test descriptions and assertions for better test coverage. - **Bug Fixes** - Modified test cases to include additional validation steps for bug fix verification. - **Documentation** - Updated test suite descriptions with new tags to reflect changes in testing strategies. - **Chores** - Adjusted file paths for test specifications to align with the updated testing focus. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2023-12-11 09:49:44 +00:00
},
);