Tests - operation in Hive - limit order create2 operation
Operation: limit_ order_create2_operation, // 21
Should be the same tests like for #485 (closed), but instead of the operation limit_ order_create_operation
the operation limit_ order_create2_operation
should be used.
Test cases:
-
1. User creates limit order Hive to HBD with {fill_or_kill} = true
and there is no matching order on the market. -
2. User creates limit order HBD to HIVE with {fill_or_kill} = true
and there is no matching order on the market. -
3. User creates limit order Hive to HBD with {fill_or_kill} = true
and there is one matching order on the market. -
4. User creates limit order HBD to HIVE with {fill_or_kill} = true
and there is one matching order on the market. -
5. User creates limit order Hive to HBD with {fill_or_kill} = true
and there are three matching orders on the market. -
6. User creates limit order HBD to HIVE with {fill_or_kill} = true
and there are three matching orders on the market. -
7. User creates limit order Hive to HBD with {fill_or_kill} = false
and there is no matching order on the market. -
8. User creates limit order HBD to HIVE with {fill_or_kill} = false
and there is no matching order on the market. -
9. User creates limit order Hive to HBD with {fill_or_kill} = false
and there is a one fully matching order on the market. -
10. User creates limit order HBD to HIVE with {fill_or_kill} = false
and there is a one fully matching order on the market. -
11. User creates limit order Hive to HBD with {fill_or_kill} = false
and the matching order comes later. -
12. User creates limit order HBD to HIVE with {fill_or_kill} = false
and the matching order comes later. -
13. User creates limit order Hive to HBD with {fill_or_kill} = false
and there is a partially matching order on the market, the second matching order comes later. -
14. User creates limit order HBD to HIVE with {fill_or_kill} = false
and there is a partially matching order on the market, the second matching order comes later. -
15. User creates limit order Hive to HBD with {fill_or_kill} = false
and the matching orders are coming later. -
16. User creates limit order HBD to HIVE with {fill_or_kill} = false
and the matching orders are coming later. -
17. User creates limit order Hive to HBD with {fill_or_kill} = false
and there is a partially matching order on the market and then the order expires. -
18. User creates limit order HBD to HIVE with {fill_or_kill} = false
and there is a partially matching order on the market and then the order expires. -
19. User creates limit order Hive to HBD with {fill_or_kill} = false
and the partially matching orders are coming later. -
20. User creates limit order HBD to HIVE with {fill_or_kill} = false
and the partially matching orders are coming later. -
21. User creates limit order Hive to HBD with {fill_or_kill} = false
and there are three matching orders on the market but later the order expires. -
22. User creates limit order HBD to HIVE with {fill_or_kill} = false
and there are three matching orders on the market but later the order expires. -
23. User creates limit order Hive to HBD with {fill_or_kill} = false
and the matching orders are coming later but later the order expires. -
24. User creates limit order HBD to HIVE with {fill_or_kill} = false
and the matching orders are coming later but later the order expires. -
25. User creates limit order Hive to HBD with {fill_or_kill} = false
and there is a partially matching order on the market, the second matching order comes later and then the order expires. -
26. User creates limit order HBD to HIVE with {fill_or_kill} = false
and there is a partially matching order on the market, the second matching order comes later and then the order expires.
Edited by Mateusz Kudela