The "editor_open" event should be logged when the user first lands in the editor but not when the user goes back to the editor from steps that logically happen inside the editor. Those steps include "edit a sentence" and "Preview and publish".
Steps
- From the dashboard, select a section suggestion
- Choose a section to translate and click "Translate this section" to go to the editor
- Observe that a "editor_open" event is being logged (this is good)
- Click the "edit translation" button at the bottom of the screen
- From the "Edit translation" screen, click the close (x) or confirm (>) button to go back to the editor
Actual
- Observe that a "editor_open" event is logged
Expected
- No "editor_open" event should be logged at this time
Derived Requirement
Ensure that the #editor_open event is logged only when the user first lands in the editor, and not when returning from in-editor steps such as "Edit translation" or "Preview and publish".
Test Steps
Test Case 1: Ensure #editor_open event is logged only on initial entry to the editor
- From the unified dashboard, select a section suggestion.
- Choose a section to translate and click the 'Translate this section' button.
- Observe the logged events using instrumentation or browser dev tools.
- ✅❓❌⬜ AC1: Confirm that the #editor_open event is logged when first landing in the editor.
Test Case 2: Ensure #editor_open event is not logged when returning from "Edit translation" step
- In the editor, click the "Edit translation" button at the bottom of the screen.
- From the "Edit translation" screen, click either the close (X) or confirm (>) button to return to the main editor.
- Observe the logged events.
- ✅❓❌⬜ AC2: Confirm that the #editor_open event is not logged upon returning from the in-editor "Edit translation" screen.
QA Results - Test Wiki
| AC | Status | Details |
|---|---|---|
| 1 | ✅ | T391502#10784164 |
| 2 | ✅ | T391502#10784164 |
