yesBad/proton-bridge
1
0
Fork 0
forked from Silverfish/proton-bridge
Code Actions Activity

feat(GODT-2538): implement smart picking of default IMAP/SMTP ports

Browse Source
This commit is contained in:
Xavier Michelon
2023-04-06 15:08:41 +02:00
parent 54b209f9e1
commit 3ddd88e127
9 changed files with 182 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
tests/features/bridge/default_ports.feature Normal file
View File

@ -0,0 +1,24 @@
Feature: Bridge picks default ports wisely
Scenario: bridge picks ports for IMAP and SMTP using default values.
When bridge starts
Then bridge IMAP port is 1143
Then bridge SMTP port is 1025
Scenario: bridge picks ports for IMAP wisely when default port is busy.
When the network port 1143 is busy
And bridge starts
Then bridge IMAP port is 1144
Then bridge SMTP port is 1025
Scenario: bridge picks ports for SMTP wisely when default port is busy.
When the network port range 1025-1030 is busy
And bridge starts
Then bridge IMAP port is 1143
Then bridge SMTP port is 1031
Scenario: bridge picks ports for IMAP SMTP wisely when default ports are busy.
When the network port range 1025-1200 is busy
And bridge starts
Then bridge IMAP port is 1201
Then bridge SMTP port is 1202

29
tests/features/bridge/updates.feature Normal file
View File

@ -0,0 +1,29 @@
Feature: Bridge checks for updates
Scenario: Update not available
Given bridge is version "2.3.0" and the latest available version is "2.3.0" reachable from "2.3.0"
When bridge starts
Then bridge sends an update not available event
Scenario: Update available without automatic updates enabled
Given bridge is version "2.3.0" and the latest available version is "2.4.0" reachable from "2.3.0"
And the user has disabled automatic updates
When bridge starts
Then bridge sends an update available event for version "2.4.0"
Scenario: Update available with automatic updates enabled
Given bridge is version "2.3.0" and the latest available version is "2.4.0" reachable from "2.3.0"
When bridge starts
Then bridge sends an update installed event for version "2.4.0"
Scenario: Manual update available with automatic updates enabled
Given bridge is version "2.3.0" and the latest available version is "2.4.0" reachable from "2.4.0"
When bridge starts
Then bridge sends a manual update event for version "2.4.0"
Scenario: Update is required to continue using bridge
Given there exists an account with username "user" and password "password"
And bridge is version "2.3.0" and the latest available version is "2.3.0" reachable from "2.3.0"
And the API requires bridge version at least "2.4.0"
When bridge starts
And the user logs in with username "user" and password "password"
Then bridge sends a forced update event