Tables Document

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