astafev / vscode-plugin-xo-qa-maintenance Goto Github PK

ideally:
for all levels show something like
passedCount/failedCount/unknownCount

the original came because of suffering that ReponseTek was causing. In other projects we can have multiple CI jobs, it would be a nice idea to pull them.

noticed during development: the tmp directory might not get deleted (though it would've been a logical thing judging my the lib's API).

Need to be checked.

• db init script
• push to the marketplace
• test on linux

example: https://github.com/microsoft/vscode-extension-samples/tree/master/comment-sample (though too invasive)

• use normal icons
• try to find a way to borrow icons shown in the default file view.

• a function to clear all records older than some period;
• ability to keep the db less than some configurable size;
• advanced: allow to configure user script to clean up some specific data.

Add debugging if possible everywhere where the run is present

Missing features:

• search with ctrl + F;
• history (previous builds);

probably SQLite was a bad choice:

1. It's difficult to launch with NodeJS,
2. probably we could benefit from storing raw json files (object-oriented db).

The plugin tries to link together allure, jenkins and local IDE. There's nothing that would be specific to the framework/the organization. Let's be developing with the idea that it'll be general plugin for those tools with some configuration.

• replace IdTitle with Title where possible
• extract root path to the config (it would be done in any case)
• ...

Idea: add somewhere a command to rerun/redebug the previously run command.

Not clear for me how the logs would look like.

Check https://getpino.io/#/

• when clicking on test cases - navigate to the code
• status for the test cases
• command for test case: run
• command for a file
• status or icon for e2e
• command for test case: show with details
• command: refresh

Later:

• status for the top folders
• info: success/total on the level of top folders
• command for folders: run
• how difficult is it to borrow commands from file explorer? how difficult it is to make everything in default explorer?

Ideas/Problems:

• Problem with icons: there're types we know better than the file explorer (helpers, constants, e2e files), but when there're js files, general ts files, etc, we'd better to borrow from the default view.

• wait until a particular build is done
• listen for a job, load all builds.

• make sure it can be easily changed for the project
• write documentation on how to update configuration
• write a cheat sheet for myself how to extract a property to the config.