Test - TUI - Saving a transaction
Test cases - Saving a transaction
Preconditions:
- The user starts on the Dashboard view.
- There is a created profile.
- The transaction contains always one transfer.
I. Test cases: Clive is activate and there is a defined key in the profile.
Remark:
The transaction contains one transfer.
-
1.1. The user saves a transaction with signature in the json format. -
1.2. The user saves a transaction without signature in the json format. -
1.3. The user saves a transaction with signature in the binary format. -
1.4. The user saves a transaction without signature in the binary format.
To check:
- The transaction is saved correctly (we can discuss how to check...)
II. Test cases: Clive is inactivate and there is a defined key in the profile.
Remark:
The transaction contains one transfer.
-
2.1. The user saves a transaction with signature in the json format. -
2.2. The user saves a transaction without signature in the json format. -
2.3. The user saves a transaction with signature in the binary format. -
2.4. The user saves a transaction without signature in the binary format.
To check:
- In case 2.1 and 2.3 clive should ask about activation.
- The transaction is saved correctly (we can discuss how to check...).
III. Test cases: Clive is activate and there is no defined key in the profile.
Remark:
The transaction contains one transfer.
-
3.1. The user saves a transaction with signature in the json format (impossible - validation). -
3.2. The user saves a transaction without signature in the json format. -
3.3. The user saves a transaction with signature in the binary format (impossible - validation). -
3.4. The user saves a transaction without signature in the binary format.
To check:
- The transaction is saved correctly if saved (we can discuss how to check...).
IV. Test cases: Clive is inactivate and there is no defined key in the profile.
Remark:
The transaction contains one transfer.
-
4.1. The user saves a transaction with signature in the json format (impossible - validation). -
4.2. The user saves a transaction without signature in the json format. -
4.3. The user saves a transaction with signature in the binary format (impossible - validation). -
4.4. The user saves a transaction without signature in the binary format.
To check:
- The transaction is saved correctly if saved (we can discuss how to check...).
Edited by Aleksandra Grabowska