---
title: Tables Document
slug: cypress-smoke-tests-qa3-env-domain-7
docTags:
createdAt: 2026-03-19T16:11:53.461Z
---
| **Test Case ID ** | **TC-EDITOR-BUTTON-001 ** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Button" option is correctly displayed in the "Add blocks" dropdown menu with proper styling and shortcut information. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Type "/" character to trigger the "Add blocks" menu .
5. Wait for the dropdown menu to appear and verify dropdown is visible.
6. Locate the "Button" option in the dropdown list.
7. Verify the "Button" option is displayed with correct styling. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "/" character triggers the "Add blocks" dropdown menu.
3. Dropdown menu appears and is visible on screen.
4. "Button" option is present in the dropdown list and has correct syling.
5. "Button" option appears in its default, unselected state.
6. "Button" option appears clickable and selectable. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should display “Button” option correctly in Add blocks dropdown
**Test ID:** AUTO-TC-EDITOR-BUTTON-001 |
| **Test Case ID** | **TC-EDITOR-BUTTON-002** |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Button" block can be created and displayed correctly using the "/" menu selection. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Type "/" character to open the "/" menu.
5. Wait for the dropdown menu to appear and verify dropdown is visible.
6. Locate the "Button" option in the dropdown list and select it.
7. Verify the "Button" block is created |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "/" character triggers the "Add blocks" dropdown menu.
3. Dropdown menu appears and is visible on screen.
4. Clicking "Button" from "Add blocks" menu transforms the block into a "Button" block.
5. Empty "Button" appears with placeholder text.
6. "Button" block is in editable state and ready for text input.
7. User can immediately start typing to replace placeholder text.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should create “Button” block via "/" menu selection
**Test ID:** AUTO-TC-EDITOR-BUTTON-002 |
| **Test Case ID** | **TC-EDITOR-BUTTON-003** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Button" block can be created and displayed correctly using the "(button)" shortcut. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Type "(button) + space key" to create the "Button" block.
5. Type a space character immediately after "\[]".
6 Verify the "Button" block is created |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. "Button" block is in editable state and ready for text input.
5. User can immediately start typing to replace placeholder text.
6. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should create “Button” block via “(button)” shortcut
**Test ID:** AUTO-TC-EDITOR-BUTTON-003 |
| **Test Case ID** | **TC-EDITOR-BUTTON-004** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that a single character can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5 Verify the "Button" block is created
6. Type the "Single Character" text in the "Button" block.
7. Verify the "Single Character" text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the "Single Character" text.
6. "Single Character" text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display single character in “Button” block
**Test ID:** AUTO-TC-EDITOR-BUTTON-004 |
| **Test Case ID** | **TC-EDITOR-BUTTON-005** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that a "Button" block can be emptied of all text and handles empty state correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
3. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created
6. Clear the placeholder text from "Button" block.
7. Verify the empty "Button" block displays correctly. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to clear the placeholder text in "Button" block.
5. "Button" block accepts the clearing of the placeholder text.
6. "Button" block maintains its styling.
7. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display empty "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-005 |
| **Test Case ID** | **TC-EDITOR-BUTTON-006** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that a single word can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type a single word text in the "Button" block.
7. Verify the single word text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the single word text.
6. Single word text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display single word in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-006 |
| **Test Case ID** | **TC-EDITOR-BUTTON-007** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that multiple words can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type multiple words text in the "Button" block.
7. Verify the multiple words text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the multiple words text.
6. Multiple words text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display multiple words in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-007 |
| **Test Case ID** | **TC-EDITOR-BUTTON-008** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that special characters can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type special characters text in the "Button" block.
7. Verify the special characters text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the special characters text.
6. Special characters text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display special characters in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-008 |
| **Test Case ID** | **TC-EDITOR-BUTTON-009** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that leading and trailing spaces can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text with leading and trailing spaces in the "Button" block.
7. Verify the text with leading and trailing spaces is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the text with leading and trailing spaces.
6. Text with leading and trailing spaces typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display leading and trailing spaces in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-009 |
| **Test Case ID** | **TC-EDITOR-BUTTON-010** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that long text can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type long text in the "Button" block.
7. Verify the long text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the long text.
6. Long text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display long text in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-010 |
| **Test Case ID** | **TC-EDITOR-BUTTON-011** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that very long text can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type very long text in the "Button" block.
7. Verify the very long text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the very long text.
6. Very long text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display very long text in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-011 |
| **Test Case ID** | **TC-EDITOR-BUTTON-012** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that Unicode characters can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type Unicode characters text in the "Button" block.
7. Verify the Unicode characters text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the Unicode characters text.
6. Unicode characters text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display Unicode characters in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-012 |
| **Test Case ID** | **TC-EDITOR-BUTTON-013** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that emojis can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type emojis text in the "Button" block.
7. Verify the emojis text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the emojis text.
6. Emojis text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display emojis in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-013 |
| **Test Case ID** | **TC-EDITOR-BUTTON-014** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that mixed case text can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type mixed case text in the "Button" block.
7. Verify the mixed case text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the mixed case text.
6. Mixed case text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display mixed case text in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-014 |
| **Test Case ID** | **TC-EDITOR-BUTTON-015** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that numbers can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type numbers text in the "Button" block.
7. Verify the numbers text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the numbers text.
6. Numbers text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display numbers in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-015 |
| **Test Case ID** | **TC-EDITOR-BUTTON-016** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that HTML-like characters can be typed in a "Button" block and displays correctly. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type HTML-like characters text in the "Button" block.
7. Verify the HTML-like characters text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can immediately start typing to replace placeholder text in "Button" block.
5. "Button" block accepts the HTML-like characters text.
6. HTML-like characters text typed replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display HTML-like characters in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-016 |
| **Test Case ID** | **TC-EDITOR-BUTTON-017** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that pasted plain text can be displayed correctly in a "Button" block. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Copy plain text from an external source.
7. Paste the plain text into the "Button" block.
8. Verify the pasted plain text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can paste plain text into "Button" block.
5. "Button" block accepts the pasted plain text.
6. Pasted plain text replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display pasted plain text in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-017 |
| **Test Case ID** | **TC-EDITOR-BUTTON-018** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that pasted very long text can be displayed correctly in a "Button" block. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Copy very long text from an external source.
7. Paste the very long text into the "Button" block.
8. Verify the pasted very long text is displayed correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can paste very long text into "Button" block.
5. "Button" block accepts the pasted very long text.
6. Pasted very long text replaces the placeholder text.
7. "Button" block maintains its styling.
8. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should accept and display pasted very long text in "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-018 |
| **Test Case ID** | **TC-EDITOR-BUTTON-019** |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Button" block text persists correctly after browser refresh. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type a text in the "Button" block.
7. Verify the text is displayed correctly in the "Button" block.
8. Refresh the browser page.
9. Wait for the document to fully load after refresh.
10. Verify the "Button" block text is persisted and displayed correctly. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is saved in the "Button" block.
6. Browser refresh completes successfully.
7. Document loads after refresh with the "Button" block.
8. "Button" block text is persisted and matches the text entered before refresh.
9. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should persist "Button" block text after browser refresh
**Test ID:** AUTO-TC-EDITOR-BUTTON-019 |
| **Test Case ID** | **TC-EDITOR-BUTTON-020** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that keyboard shortcuts (copy, paste, undo, redo) work correctly in a "Button" block. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Select the text in the "Button" block.
8. Use keyboard shortcut to copy the text.
9. Use keyboard shortcut to paste the text.
10. Use keyboard shortcut to undo the action.
11. Use keyboard shortcut to redo the action.
12. Verify all keyboard shortcuts work correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text can be selected in "Button" block.
6. Copy keyboard shortcut copies the selected text.
7. Paste keyboard shortcut pastes the copied text.
8. Undo keyboard shortcut reverts the last action.
9. Redo keyboard shortcut reapplies the reverted action.
10. All keyboard shortcuts function correctly in "Button" block.
11. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should support keyboard shortcuts in "Button" block \[copy, paste, undo, redo]
**Test ID:** AUTO-TC-EDITOR-BUTTON-020 |
| **Test Case ID** | **TC-EDITOR-BUTTON-021** |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that a word can be selected and replaced from "Button" text. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text containing multiple words in the "Button" block.
7. Select a word from the "Button" text.
8. Type new text to replace the selected word.
9. Verify the word is replaced correctly in the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Word can be selected from "Button" text.
6. Selected word is highlighted.
7. Typing new text replaces the selected word.
8. "Button" block maintains its styling.
9. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow selecting and replacing word from "Button" text
**Test ID:** AUTO-TC-EDITOR-BUTTON-021 |
| **Test Case ID** | **TC-EDITOR-BUTTON-022** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that individual characters can be deleted from "Button" text. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Position the cursor at a specific character in the "Button" text.
8. Use Backspace key to remove individual characters.
9. Verify individual characters are deleted correctly from the "Button" text. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Cursor can be positioned at any character in "Button" text.
6. Backspace key deletes the character before the cursor.
7. Characters are removed correctly from "Button" text.
8. "Button" block maintains its styling.
9. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow deleting individual characters from "Button" text
**Test ID:** AUTO-TC-EDITOR-BUTTON-022 |
| **Test Case ID** | **TC-EDITOR-BUTTON-023** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that text can be inserted in the middle of a "Button" block. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Position the cursor in the middle of the "Button" text.
8. Type additional text at the cursor position.
9. Verify the text is inserted correctly in the middle of the "Button" block. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Cursor can be positioned in the middle of "Button" text.
6. Typing at the cursor position inserts text in the middle.
7. Existing text is preserved and shifted to accommodate inserted text.
8. "Button" block maintains its styling.
9. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow inserting text in middle of "Button" block
**Test ID:** AUTO-TC-EDITOR-BUTTON-023 |
| **Test Case ID** | **TC-EDITOR-BUTTON-024** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Button" block can be indented using Tab key. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Type text in the "Button" block.
6. Verify the "Button" block is created.
7. Click on the "Button" block to select it.
8. Press Tab key to indent the "Button" block.
9. Verify the "Button" block is indented correctly. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. "Button" block can be selected.
6. Tab key indents the "Button" block.
7. "Button" block displays with increased indentation.
8. "Button" block maintains its styling.
9. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow indenting "Button" block with Tab key
**Test ID:** AUTO-TC-EDITOR-BUTTON-024 |
| **Test Case ID** | **TC-EDITOR-BUTTON-025** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Button" block can be outdented using Shift+Tab key. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Type text in the "Button" block.
6. Verify the "Button" block is created.
7. Indent the "Button" block using Tab key.
8. Click on the "Button" block to select it.
9. Press Shift+Tab key to outdent the "Button" block.
10. Verify the "Button" block is outdented correctly. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. "Button" block can be indented using Tab key.
6. "Button" block can be selected.
7. Shift+Tab key outdents the "Button" block.
8. "Button" block displays with decreased indentation.
9. "Button" block maintains its styling.
10. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow outdenting "Button" block with Shift+Tab key
**Test ID:** AUTO-TC-EDITOR-BUTTON-025 |
| **Test Case ID** | **TC-EDITOR-BUTTON-026** |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Internal Link" is displayed as the default tab for default "Button". |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Verify "Internal Link" tab is displayed as the default tab. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "Internal Link" tab is visible and active by default.
9. "Internal Link" tab is the selected tab.
10. "Button" block maintains its styling.
11. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should display "Internal Link" as the default tab for default "Button"
**Test ID:** AUTO-TC-EDITOR-BUTTON-026 |
| **Test Case ID** | **TC-EDITOR-BUTTON-027** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "External Link" default tab is displayed correctly for default "Button". |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Click on the "External Link" tab.
10. Verify the "External Link" tab is displayed correctly. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "External Link" tab is visible in the settings popover.
9. Clicking "External Link" tab switches to the "External Link" tab.
10. "External Link" tab displays correctly with all its options.
11. "Button" block maintains its styling.
12. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should display "External Link" default tab correctly for default "Button"
**Test ID:** AUTO-TC-EDITOR-BUTTON-027 |
| **Test Case ID** | **TC-EDITOR-BUTTON-028** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that the text changes from empty "Button" to Button when selecting first document in "Internal Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document.
3. At least one document exists in the workspace. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Clear the text from "Button" block to make it empty.
8. Click on the setting button from "Button" block to open the settings popover.
9. Verify the "Button" settings popover is displayed.
10. Verify "Internal Link" tab is displayed.
11. Select a document in the "Recent Docs" section.
12. Verify the "Button" text changes from empty to Button. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Text can be cleared from "Button" block.
7. "Button" block is empty after clearing text.
8. Clicking on setting button from "Button" block opens the settings popover.
9. "Button" settings popover is displayed.
10. "Internal Link" tab is displayed.
11. Documents are available in the "Recent Docs" section.
12. Document can be selected from the "Recent Docs" section.
13. "Button" text changes from empty to Button after document selection.
14. "Button" block maintains its styling.
15. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should change the text from empty "Button" to Button when selecting first document in "Internal Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-028 |
| **Test Case ID** | **TC-EDITOR-BUTTON-029** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Test Case Description** | Verify that the text changes from default "Button" to Button when selecting first document in "Internal Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document.
3. At least one document exists in the workspace. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created with default "Button" text.
6. Click on the setting button from "Button" block to open the settings popover.
7. Verify the "Button" settings popover is displayed.
8. Verify "Internal Link" tab is displayed.
9. Select a document in the "Recent Docs" section.
10. Verify the "Button" text changes from typed text to Button. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text showing default "Button" text.
4. Clicking on setting button from "Button" block opens the settings popover.
5 "Button" settings popover is displayed.
6. "Internal Link" tab is displayed.
7. Documents are available in the "Recent Docs" section.
8. Document can be selected from the "Recent Docs" section.
9. "Button" text changes from placeholder text to Button after document selection.
10. "Button" block maintains its styling.
11. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should change the text from default "Button" to Button when selecting first document in "Internal Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-029 |
| **Test Case ID** | **TC-EDITOR-BUTTON-030** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that the text does not change from filled "Button" to Button when selecting first document in "Internal Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document.
3. At least one document exists in the workspace. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type custom text in the "Button" block to fill it.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Verify "Internal Link" tab is displayed.
10. Select a document in the "Recent Docs" section.
11. Verify the "Button" text does not change and remains as the custom filled text. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type custom text in "Button" block.
5. Custom text replaces the placeholder text.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "Internal Link" tab is displayed.
9. Documents are available in the "Recent Docs" section.
10. Document can be selected from the "Recent Docs" section.
11. "Button" text does not change and remains as the custom filled text after document selection.
12. "Button" block maintains its styling.
13. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should not change the text from filled "Button" to Button when selecting first document in "Internal Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-030 |
| **Test Case ID** | **TC-EDITOR-BUTTON-031** |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Heading" can be selected for "Set anchor" option when having a document selected in "Internal Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document.
3. At least one document exists in the workspace.
4. Selected document has at least one "Heading" block. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Verify "Internal Link" tab is displayed.
10. Select a document in the "Recent Docs" section.
11. Locate the "Set anchor" dropdown in the "Internal Link" tab.
12. Select a "Heading" from the "Set anchor" dropdown.
13. Verify the "Heading" is selected in the dropdown for "Set anchor" option. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "Internal Link" tab is displayed.
9. Documents are available in the "Recent Docs" section.
10. Document can be selected from the "Recent Docs" section.
11. "Set anchor" dropdown is available in the "Internal Link" tab.
12. "Heading" options are available in the "Set anchor" dropdown.
13. "Heading" can be selected from the "Set anchor" dropdown.
14. Selected "Heading" is displayed in the "Set anchor" dropdown.
15. "Button" block maintains its styling.
16. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow selecting "Heading" for "Set anchor" option when having a document select in "Internal Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-031 |
| **Test Case ID** | **TC-EDITOR-BUTTON-032** |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Heading" can be removed for "Set anchor" option when having a document selected in "Internal Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document.
3. At least one document exists in the workspace.
4. Selected document has at least one "Heading" block.
5. A "Heading" is already selected in "Set anchor" option. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Verify "Internal Link" tab is displayed.
10. Select a document in the "Recent Docs" section.
11. Locate the "Set anchor" dropdown in the "Internal Link" tab.
12. Select a "Heading" from the "Set anchor" dropdown.
13. Remove the selected "Heading" from the "Set anchor" dropdown.
14. Verify the "Heading" is removed from "Set anchor" dropdown. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "Internal Link" tab is displayed.
9. Documents are available in the "Recent Docs" section.
10. Document can be selected from the "Recent Docs" section.
11. "Set anchor" dropdown is available in the "Internal Link" tab.
12. "Heading" can be selected from the "Set anchor" dropdown.
13. Selected "Heading" is displayed in the "Set anchor" dropdown.
14. Selected "Heading" can be removed from the "Set anchor" dropdown using the remove button.
15. "Set anchor" dropdown is cleared after removing "Heading".
16. "Button" block maintains its styling.
17. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow removing "Heading" for "Set anchor" option when having a document select in "Internal Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-032 |
| **Test Case ID** | **TC-EDITOR-BUTTON-033** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Test Case Description** | Verify that "Open in new tab" switch can be turned off or on from "Internal Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document.
3. At least one document exists in the workspace. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Verify "Internal Link" tab is displayed.
10. Select a document in the "Recent Docs" section.
11. Locate the "Open in new tab" switch in the "Internal Link" tab.
12. Toggle the "Open in new tab" switch to on.
13. Verify the "Open in new tab" switch is turned on.
14. Toggle the "Open in new tab" switch to off.
15. Verify the "Open in new tab" switch is turned off. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "Internal Link" tab is displayed.
9. Documents are available in the "Recent Docs" section.
10. Document can be selected from the "Recent Docs" section.
11. "Open in new tab" switch is available in the "Internal Link" tab.
12. "Open in new tab" switch can be toggled to on.
13. "Open in new tab" switch displays as on when toggled.
14. "Open in new tab" switch can be toggled to off.
15. "Open in new tab" switch displays as off when toggled.
16. "Button" block maintains its styling.
17. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow "Open in new tab" switch turn to off or on from "Internal Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-033 |
| **Test Case ID** | **TC-EDITOR-BUTTON-034** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Test Case Description** | Verify that "Show as snippet" switch can be turned on or off from "Internal Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document.
3. At least one document exists in the workspace. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Verify "Internal Link" tab is displayed.
10. Select a document in the "Recent Docs" section.
11. Locate the "Show as snippet" switch in the "Internal Link" tab.
12. Toggle the "Show as snippet" switch to on.
13. Verify the "Show as snippet" switch is turned on.
14. Toggle the "Show as snippet" switch to off.
15. Verify the "Show as snippet" switch is turned off. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "Internal Link" tab is displayed.
9. Documents are available in the "Recent Docs" section.
10. Document can be selected from the "Recent Docs" section.
11. "Show as snippet" switch is available in the "Internal Link" tab.
12. "Show as snippet" switch can be toggled to on.
13. "Show as snippet" switch displays as on when toggled.
14. "Show as snippet" switch can be toggled to off.
15. "Show as snippet" switch displays as off when toggled.
16. "Button" block maintains its styling.
17. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow "Show as snippet" switch turn to on or off from "Internal Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-034 |
| **Test Case ID** | **TC-EDITOR-BUTTON-035** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that the selected document can be removed from "Internal Link" tab "Button". |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document.
3. At least one document exists in the workspace. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Verify "Internal Link" tab is displayed.
10. Select a document in the "Recent Docs" section.
11. Verify the document is selected.
12. Remove the selected document from the "Internal Link" tab.
13. Verify the selected document is removed. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "Internal Link" tab is displayed.
9. Documents are available in the "Recent Docs" section.
10. Document can be selected from the "Recent Docs" section.
11. Selected document is displayed in the "Internal Link" tab.
12. Selected document can be removed from the "Internal Link" tab "Recent Docs" section using remove button.
13. Document selection is cleared after removal.
14. "Button" block maintains its styling.
15. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow removing the selected document from "Internal Link" tab Button
**Test ID:** AUTO-TC-EDITOR-BUTTON-035 |
| **Test Case ID** | **TC-EDITOR-BUTTON-036** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "No docs found." message is displayed when searching invalid document in input from "Internal Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Verify "Internal Link" tab is displayed.
10. Locate the search docs input field in the "Internal Link" tab.
11. Type an invalid document name in the search docs input field.
12. Verify the "No docs found." message is displayed. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "Internal Link" tab is displayed.
9. Search docs input field is available in the "Internal Link" tab.
10. User can type in the search docs input field.
11. Invalid document name can be entered in the search docs input field.
12. "No docs found." message is displayed when searching for invalid document.
13. "Button" block maintains its styling.
14. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should display "No docs found." when searching invalid document in input from "Internal Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-036 |
| **Test Case ID** | **TC-EDITOR-BUTTON-037** |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that correct https, http and mailto URLs can be added to data in url input from "External Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Click on the "External Link" tab.
10. Locate the url input field in the "External Link" tab.
11. Type a correct https URL in the url input field.
12. Verify the https URL is accepted.
13. Clear the url input field.
14. Type a correct http URL in the url input field.
15. Verify the http URL is accepted.
16. Clear the url input field.
17. Type a correct mail address in the url input field.
18. Verify the mailto URL is accepted. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "External Link" tab is displayed.
9. Url input field is available in the "External Link" tab.
10. User can type in the url input field.
11. Correct https URL is accepted in the url input field.
12. Correct http URL is accepted in the url input field.
13. Correct mail address is accepted in the url input field.
14. All valid URL formats are accepted without error.
15. "Button" block maintains its styling.
16. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow adding correct https, http and mailto to data in url input from "External Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-037 |
| **Test Case ID** | **TC-EDITOR-BUTTON-038** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "URL is not valid" message is displayed when inserting invalid data in https, http and mailto url input from "External Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Click on the "External Link" tab.
10. Locate the url input field in the "External Link" tab.
11. Type an invalid https URL in the url input field.
12. Verify the "URL is not valid" message is displayed.
13. Clear the url input field.
14. Type an invalid http URL in the url input field.
15. Verify the "URL is not valid" message is displayed.
16. Clear the url input field.
17. Type an invalid mailto mail address in the url input field.
18. Verify the "URL is not valid" message is displayed. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "External Link" tab is displayed.
9. Url input field is available in the "External Link" tab.
10. User can type in the url input field.
11. Invalid https URL triggers "URL is not valid" message.
12. Invalid http URL triggers "URL is not valid" message.
13. Invalid mailto mail address triggers "URL is not valid" message.
14. "URL is not valid" message is displayed for all invalid URL formats.
15. "Button" block maintains its styling.
16. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should display "URL is not valid" when inserting invalid data in https, http and mailto url input from "External Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-038 |
| **Test Case ID** | **TC-EDITOR-BUTTON-039** |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that apply, copy, open in new tab options can be used in url input from "External Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Click on the "External Link" tab.
10. Locate the url input field in the "External Link" tab.
11. Type a valid URL in the url input field.
12. Locate the apply option in the url input section.
13. Click on the apply option.
14. Verify the apply option works correctly.
15. Locate the copy option in the url input section.
16. Click on the copy option.
17. Verify the copy option works correctly.
18. Locate the open in new tab option in the url input section.
19. Click on the open in new tab option.
20. Verify the open in new tab option works correctly. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "External Link" tab is displayed.
9. Url input field is available in the "External Link" tab.
10. User can type valid URL in the url input field.
11. Apply option is available in the url input section.
12. Apply option can be clicked and works correctly.
13. Copy option is available in the url input section.
14. Copy option can be clicked and works correctly.
15. Open in new tab option is available in the url input section.
16. Open in new tab option can be clicked and works correctly.
17. All options function as expected.
18. "Button" block maintains its styling.
19. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow using apply, copy, open in new tab in url input from "External Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-039 |
| **Test Case ID** | **TC-EDITOR-BUTTON-040** |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Open in new tab" switch can be turned off or on from "External Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Click on the "External Link" tab.
10. Locate the "Open in new tab" switch in the "External Link" tab.
11. Toggle the "Open in new tab" switch to on.
12. Verify the "Open in new tab" switch is turned on.
13. Toggle the "Open in new tab" switch to off.
14. Verify the "Open in new tab" switch is turned off. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "External Link" tab is displayed.
9. "Open in new tab" switch is available in the "External Link" tab.
10. "Open in new tab" switch can be toggled to on.
11. "Open in new tab" switch displays as on when toggled.
12. "Open in new tab" switch can be toggled to off.
13. "Open in new tab" switch displays as off when toggled.
14. "Button" block maintains its styling.
15. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** [cypress/e2e/EDITOR/EDITOR\_Button.cy.ts](https://github.com/Archbee/archbee-e2e/blob/main/cypress/e2e/EDITOR/EDITOR_Button.cy.ts)
**Test Name:** Should allow "Open in new tab" switch turn to off or on from "External Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-040 |
| **Test Case ID** | **TC-EDITOR-BUTTON-041** |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Test Case Description** | Verify that "Add nofollow tag" switch can be turned on or off from "External Link" tab. |
| **Preconditions** | 1. User has a document created and opened.
2. User is in edit mode of the document. |
| **Test Steps** | 1. Navigate to the document.
2. Wait for the document to fully load.
3. Click on an empty block.
4. Create a new "Button" block using "Add Blocks" menu or "(button) + space key" shortcut.
5. Verify the "Button" block is created.
6. Type text in the "Button" block.
7. Click on the setting button from "Button" block to open the settings popover.
8. Verify the "Button" settings popover is displayed.
9. Click on the "External Link" tab.
10. Locate the "Add nofollow tag" switch in the "External Link" tab.
11. Toggle the "Add nofollow tag" switch to on.
12. Verify the "Add nofollow tag" switch is turned on.
13. Toggle the "Add nofollow tag" switch to off.
14. Verify the "Add nofollow tag" switch is turned off. |
| **Expected Results** | 1. Document loads successfully and is ready for input.
2. "Add Blocks" menu or "(button) + space key" creates a "Button" block.
3. Empty "Button" appears with placeholder text.
4. User can type text in "Button" block.
5. Text is displayed in the "Button" block.
6. Clicking on setting button from "Button" block opens the settings popover.
7. "Button" settings popover is displayed.
8. "External Link" tab is displayed.
9. "Add nofollow tag" switch is available in the "External Link" tab.
10. "Add nofollow tag" switch can be toggled to on.
11. "Add nofollow tag" switch displays as on when toggled.
12. "Add nofollow tag" switch can be toggled to off.
13. "Add nofollow tag" switch displays as off when toggled.
14. "Button" block maintains its styling.
15. Document remains in edit mode. |
| **Comments** | |
| **Automation Test Case** | **Cypress Test File:** cypress/e2e/EDITOR/EDITOR\_Button.cy.ts
**Test Name:** Should allow "Add nofollow tag" switch turn to on or off from "External Link" tab
**Test ID:** AUTO-TC-EDITOR-BUTTON-041 |