Test - TUI - Loading a transaction from a file
Test cases - Saving a transaction
Preconditions:
- The user starts on the Dashboard view.
- There is a created profile.
- The transaction contains always one transfer.
- For each test there are following files needed:
- tr_sign.json
- tr_sign.bin
- tr_unsign.json
- tr_unsign.bin
I. Test cases: Clive is activate and there is a defined key in the profile.
-
1.1. The user loads the file tr_sign.json and broadcasts it. -
1.2. The user loads the file tr_sign.bin and broadcasts it. -
1.3. The user loads the file tr_unsign.json and broadcasts it. -
1.4. The user loads the file tr_unsign.bin and broadcasts it.
To check:
- If the transaction is signed, there should be a message: "This transaction is already signed."
- If the transaction is not signed,there should be "Sign with key:"
- There should be a name of the file on the view.
- It should be possible to broadcast the transaction.
II. Test cases: Clive is inactivate and there is a defined key in the profile.
-
2.1. The user loads the file tr_sign.json and broadcasts it. -
2.2. The user loads the file tr_sign.bin and broadcasts it. -
2.3. The user loads the file tr_unsign.json and broadcasts it. -
2.4. The user loads the file tr_unsign.bin and broadcasts it.
To check:
- The signed transaction - it should be possible to broadcast without activation a profile.
- The unsigned transaction - before broadcasting clive should ask about profile activation.
III. Test cases: Clive is activate and there is no defined key in the profile.
-
3.1. The user loads the file tr_sign.json and broadcasts it. -
3.2. The user loads the file tr_sign.bin and broadcasts it. -
3.3. The user loads the file tr_unsign.json and tries to broadcast it. -
3.4. The user loads the file tr_unsign.bin and tries to broadcast it.
To check:
- The signed transaction - it should be possible to broadcast without a define key.
- The unsigned transaction - the error message is displayed.
IV. Test cases: Clive is inactivate and there is no defined key in the profile.
-
4.1. The user loads the file tr_sign.json and broadcasts it. -
4.2. The user loads the file tr_sign.bin and broadcasts it. -
4.3. The user loads the file tr_unsign.json and tries to broadcast it. -
4.4. The user loads the file tr_unsign.bin and tries to broadcast it.
To check:
- The signed transaction - it should be possible to broadcast without a define key.
- The unsigned transaction - the error message is displayed.
Edited by Aleksandra Grabowska