Test - TUI - Config - Manage key aliases
Test cases - Config - Manage key aliases
Preconditions:
- The user starts on the Dashboard view.
- There is a created profile.
I. Test cases: Clive is activate and there is a defined key in the profile.
-
1. The user removes an alias and the alias is removed form TUI (I hope it is possible to check - let me know). -
2. The user edits the key alias.
To check:
- A new alias is displayed on the Transaction summary screen.
-
3. The user removes an alias and then adds a new alias with the same key (it should be possible).
To check:
- Before removing the alias, the user has to enter the password.
-
4. The user removes an alias and then adds a new alias with the different key.
To check:
- Before removing the alias, the user has to enter the password.
-
5. The user adds a new alias with the same key. (it should be impossible - there is a validation). -
6. The user adds a new alias with different key.
To check:
- There should be two aliases displayed on the Transaction summary screen.
-
7. The user adds a new key from a file.
II. Test cases: Clive is activate and there is no defined key in the profile.
-
1. The user adds a key using TUI. -
2. The user adds a new key from a file. -
3. The user adds an alias, then removes an alias and then adds a new alias with the same key (it should be possible).
To check:
- Before removing the alias, the user has to enter the password.
-
4. The user adds ans alias, then removes an alias and then adds a new alias with the different key.
To check:
- Before removing the alias, the user has to enter the password.
III. Test cases: Clive is inactive.
-
1. The user cannot go to the view Manage key aliases
, because it is not accessible.