This issue is made to plan the future development of the Debug plugin, and to keep track of the state of its development.
|
item |
estimation |
description |
link to GitHub issue |
Require |
| ✅ |
Plugin API |
n/a |
Expose the plugin API (call / emit / on) |
|
|
| ✅ |
Minimal UI |
n/a |
Create a minimal UI for the plugin to be usable by people |
|
|
| ⬜️ |
Main Panel |
1 day |
Move the UI from the side panel to the main panel (no functionality change, only refactoring) |
#2 |
|
| ⬜️ |
Better UI |
2 days |
Refactor the UI to facilitate plugin calls |
#5 |
#2 |
| ⬜️ |
Better logging |
2 days |
log info in the UI instead of in the dev console (include ui modification) |
#3 |
#2 |
| ⬜️ |
Basic automation |
1 day |
Basic test automation (list of call, assert answers) |
#4 |
#2 |
| ⬜️ |
Save/Load |
1 day |
Save/Load scenario to/from file |
#6 |
#4 |
| ⬜️ |
Complex automation (1) |
1 day |
await & assert for emit |
#7 |
#4 |
| ⬜️ |
Complex automation (2) |
2 day |
conditions : "if call/emit has return ... then execute those calls, else ..." |
#8 |
#4 |
| ⬜️ |
Complex automation (3) |
1 day |
loops : "execute this call X times" |
#9 |
#4 |
| ⬜️ |
TOTAL |
11 days |
|
|
|
This issue is made to plan the future development of the Debug plugin, and to keep track of the state of its development.