You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Wizard doesn't allow to procced without SFTP and SARIF plugin installation, but SFTP should not be required in case user wants to connect to locally installed WSL server
To Reproduce
Steps to reproduce the behavior:
Disable SFTP plugin if it's installed
Start UTBot: QuickStart wizard
Try to click 'Next' button to continue server configuration
Expected behavior
Server configuration page opened and user set ups connection to local server. There could be warning on next page or we could enable 'localhost' with message that SFTP is not available.
Actual behavior
User cannot continue configuration. Label against SFTP plugin says: "Please, install or enable the SFTP plugin and restart the wizard!"
Visual proofs (screenshots, logs)
Additional context
No sure if we should require SARIF plugin as we can generate tests without it, but at least we should not block wizard when there is no SFTP installed.
The text was updated successfully, but these errors were encountered:
Description
Wizard doesn't allow to procced without SFTP and SARIF plugin installation, but SFTP should not be required in case user wants to connect to locally installed WSL server
To Reproduce
Steps to reproduce the behavior:
UTBot: QuickStart
wizardExpected behavior
Server configuration page opened and user set ups connection to local server. There could be warning on next page or we could enable 'localhost' with message that SFTP is not available.
Actual behavior
User cannot continue configuration. Label against SFTP plugin says: "Please, install or enable the SFTP plugin and restart the wizard!"
Visual proofs (screenshots, logs)
Additional context
No sure if we should require SARIF plugin as we can generate tests without it, but at least we should not block wizard when there is no SFTP installed.
The text was updated successfully, but these errors were encountered: