|
| 1 | +# Web Studio Bug Backlog |
| 2 | + |
| 3 | +## Usage |
| 4 | + |
| 5 | +Each bug entry should contain: |
| 6 | + |
| 7 | +- identifier |
| 8 | +- affected area |
| 9 | +- reproduction steps |
| 10 | +- expected behavior |
| 11 | +- bug behavior |
| 12 | +- status |
| 13 | + |
| 14 | +## List of Bugs |
| 15 | + |
| 16 | +### WS-001 CLI Buttons Not Recomputed After Workspace Change |
| 17 | + |
| 18 | +- Area: CLI Mode |
| 19 | +- Status: fixed |
| 20 | + |
| 21 | +Reproduction: |
| 22 | + |
| 23 | +1. Open CLI mode with a non-CLI workspace selected. |
| 24 | +2. Switch workspace to `cli_generic`. |
| 25 | +3. Enter a target. |
| 26 | + |
| 27 | +Expected: |
| 28 | + |
| 29 | +- CLI start buttons enable immediately if the selected workspace is CLI-compatible |
| 30 | + |
| 31 | +Bug: |
| 32 | + |
| 33 | +- CLI start buttons remained disabled until view remount or page switching |
| 34 | + |
| 35 | +Acceptance: |
| 36 | + |
| 37 | +- CLI availability recomputes immediately when workspace changes |
| 38 | + |
| 39 | +### WS-002 Runtime Pages Missing SUT Target Summary |
| 40 | + |
| 41 | +- Area: Generate Mode / Spy Mode |
| 42 | +- Status: fixed |
| 43 | + |
| 44 | +Reproduction: |
| 45 | + |
| 46 | +1. Select a workspace with `SUTConnectorValue`. |
| 47 | +2. Open Generate or Spy page. |
| 48 | + |
| 49 | +Expected: |
| 50 | + |
| 51 | +- runtime header shows the current `SUTConnectorValue` |
| 52 | + |
| 53 | +Bug: |
| 54 | + |
| 55 | +- summary was absent or displayed `No SUT configured.` |
| 56 | + |
| 57 | +Acceptance: |
| 58 | + |
| 59 | +- runtime header displays normalized `SUTConnectorValue` |
| 60 | +- quoted values are rendered without wrapping quotes |
| 61 | + |
| 62 | +### WS-003 Java Policy Editor Close Kept Modal Open |
| 63 | + |
| 64 | +- Area: Test Configuration / Java Policies |
| 65 | +- Status: fixed |
| 66 | + |
| 67 | +Reproduction: |
| 68 | + |
| 69 | +1. Open `Edit Java Policies`. |
| 70 | +2. Select or create a Java policy source so the policy source editor modal opens. |
| 71 | +3. Click `Close`. |
| 72 | + |
| 73 | +Expected: |
| 74 | + |
| 75 | +- the policy source editor modal closes |
| 76 | +- the user returns to the Java policies overview |
| 77 | + |
| 78 | +Bug: |
| 79 | + |
| 80 | +- the modal remained open because the selected policy source was not cleared |
| 81 | + |
| 82 | +Acceptance: |
| 83 | + |
| 84 | +- closing the policy source editor clears the selected policy source |
| 85 | +- the modal condition becomes false after clicking `Close` |
| 86 | +- regression test `policyEditorState.test.js` passes |
| 87 | + |
| 88 | +### WS-004 Failed Save And Compile Guard Hid Java Diagnostics |
| 89 | + |
| 90 | +- Area: Test Configuration / Java Composition and Java Policies |
| 91 | +- Status: fixed |
| 92 | + |
| 93 | +Reproduction: |
| 94 | + |
| 95 | +1. Open `Edit Java Composition Flow`. |
| 96 | +2. Open a Java composition source, such as `WebdriverParabankTestSequenceLoginCapability.java`. |
| 97 | +3. Edit the source so Java compilation fails. |
| 98 | +4. Switch to another configuration view. |
| 99 | +5. In the unsaved and uncompiled dialog, click `Save and Compile`. |
| 100 | + |
| 101 | +Expected: |
| 102 | + |
| 103 | +- compilation fails |
| 104 | +- pending navigation is aborted |
| 105 | +- the unsaved and uncompiled dialog closes |
| 106 | +- the Java source editor remains visible with compilation diagnostics |
| 107 | + |
| 108 | +Bug: |
| 109 | + |
| 110 | +- the unsaved and uncompiled dialog remained open, preventing the user from inspecting the Java source editor and diagnostics |
| 111 | + |
| 112 | +Acceptance: |
| 113 | + |
| 114 | +- failed compile from the guard closes the guard dialog |
| 115 | +- failed compile does not execute the pending navigation |
| 116 | +- Java source editor stays visible with compilation diagnostics |
0 commit comments