Update a few manual tests
This commit is contained in:
1 parent
03ac5035fc
commit
f474af1925
7 files changed
+30
-35
No files matched your search
@@ -1,8 +1,8 @@
|
||||
This test verifies that clip limits are followed, and rule presedence works correctly
|
||||
This test verifies that clip limits are followed, and rule precedence works correctly
|
||||
|
||||
1. Pick a future, lets say ESU8.
|
||||
|
||||
2. In the risk admin, go to accounts and select the default account for your user (let say ACC A1).
|
||||
2. In the AdminUI, go to accounts and select the default account for your user (let say ACC A1).
|
||||
Go to Position Limits and enter large values (for both security and product level), so that
|
||||
position limits are bypassed.
|
||||
|
||||
@@ -21,4 +21,4 @@ Enter a Clip Size of 10. Make sure orders > 10 are rejected and < 10 are allowed
|
||||
|
||||
10. Verify that ESU8 is still controlled by a clip size of 10.
|
||||
|
||||
11. Enter a future spread order. It should be rejected since we dont have any clip limits for futures.
|
||||
11. Enter a future spread order. It should be rejected since we don't have any clip limits for futures.
|
||||
@@ -17,22 +17,17 @@ Prerequisites
|
||||
User settings
|
||||
-------------
|
||||
3. Navigate to http://sparkvm:8000 (or wherever your sparkd resides), Users tab
|
||||
4. Btween bts and bts_2 users, verify that have distinct operator ids
|
||||
4. Btween bts and bts_2 users, verify that have distinct operator ids (Order Routing tab)
|
||||
5. In another ssh session on your server, let's tail the sim fix log for orders
|
||||
tail -f ~/sparkdata/data/jetfix/sim/current/fix | grep --line-buffered 35=D | tr '\001' '|'
|
||||
6. Open up a client, login as bts, pick your favorite symbol and submit an order
|
||||
7. Your tail should show the fix from the order. Scan the line for 50={operator id}. The operator id found should match the value from the web ui.
|
||||
7. Your tail should show the fix from the order. Scan the line for 50={operator id}. The operator id found should match the value from the AdminUI.
|
||||
8. Change your user's operator's id, submit a new order, and verify the new value is being sent out on the tag 50
|
||||
9. Relaunch the gui and login as bts_2
|
||||
10. Submit an order and verify the tag 50 matches what is specified in the web ui
|
||||
10. Submit an order and verify the tag 50 matches what is specified in the AdminUI
|
||||
|
||||
Account settings
|
||||
-----------------
|
||||
11. Within the web UI, switch over to Accounts and choose an account in which your users can trade (ACC A1), then switch to the exchange settings tab
|
||||
12. Place an order and check that the CTI Code, Origin, and Clearing Accont match what is specified in the web ui
|
||||
11. Within the AdminUI, switch over to Accounts and choose an account in which your users can trade (ACC A1), then switch to the exchange settings tab
|
||||
12. Place an order and check that the CTI Code, Origin, and Clearing Account match what is specified in the AdminUI
|
||||
13. Change the values, place another order, and verify the new values are being sent
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
This test verifies that product position limits are enforced correctly. (Position limits are
|
||||
enforced at both the security and account level)
|
||||
|
||||
0. Clear up your orders and fills so we dont have any lingering positions
|
||||
0. Clear up your orders and fills so we don't have any lingering positions
|
||||
(run rm -r orders and rm -r fills from /sparkdata/data/databases). Restart your sparkd
|
||||
|
||||
1. Pick 2 futures, lets say SIU8 and SIZ8
|
||||
|
||||
2. In the risk admin, select the default account for your user (lets say ACC A1)
|
||||
and enter big clip limits so that clip limits dont interfare with this test.
|
||||
2. In the AdminUI, select the default account for your user (lets say ACC A1)
|
||||
and enter big clip limits so that clip limits don't interfere with this test.
|
||||
|
||||
3. Go to the Position limits and remove all entries at both the product and security level
|
||||
|
||||
|
||||
@@ -1,24 +1,24 @@
|
||||
This test verifies that security position limits are enforced correctly. (Position limits are
|
||||
enforced at both the security and account level)
|
||||
|
||||
0. Clear up your orders and fills so we dont have any lingering positions
|
||||
0. Clear up your orders and fills so we don't have any lingering positions
|
||||
(run rm -r orders and rm -r fills from /sparkdata/data/databases). Restart your sparkd
|
||||
|
||||
1. Pick a future, lets say ESU8 and an account, lets say ACC A1.
|
||||
|
||||
2. In the risk admin, select the default account for your user, and enter big clip limits so that
|
||||
clip limits dont interfare with this test.
|
||||
2. In the AdminUI, select the default account for your user, and enter big clip limits so that
|
||||
clip limits don't interfere with this test.
|
||||
|
||||
3. Go to the Position limits and remove all entries at both the product and security level
|
||||
|
||||
4. Enter an ESU8 order. It should be rejected. Make sure the rejection message makes sense
|
||||
|
||||
5. Now enter a product level rule for GLBX, Future, ES, 1,000,000, 1,000,000 (to bypass it),
|
||||
5. Now enter a product level rule for GLBX, Future, ES, 1,000,000, 1,000,000 (to bypass it),
|
||||
and a security level rule GLBX, Future, ES, 50, 100
|
||||
|
||||
6. Enter a 10 lot. This brings our 'position' to 10 (where 'positions' = fills + working orders).
|
||||
Enter more orders to get it to 50. Now try to get past 50 and you should be stopped with a clear message.
|
||||
Dont cancel these yet.
|
||||
don't cancel these yet.
|
||||
|
||||
6. Now start selling 10 lots. Since we are already long 50, and our short limit is 100, we can go all
|
||||
the way to 150 (net 100 short), but not beyond that. Verify that.
|
||||
@@ -26,9 +26,9 @@ the way to 150 (net 100 short), but not beyond that. Verify that.
|
||||
8. Cancel all your buy orders. Cancel some of your sell orders to get the net short position to 50.
|
||||
Start selling again, and make sure you are stopped at 100.
|
||||
|
||||
9. Try another future, lets say SIU8. Since we dont have a position rule for it, it should fail.
|
||||
9. Try another future, lets say SIU8. Since we don't have a position rule for it, it should fail.
|
||||
|
||||
10. Enter a new rule for the product (and use * for the symbol) and enter 10 for the long and short limits.
|
||||
10. Enter a new rule for the product (and use All for the symbol) and enter 10 for the long and short limits.
|
||||
|
||||
11. Now enter a 1 lot SIU8 again. Keep buying more and make sure you are stopped at the long limit of 10.
|
||||
|
||||
|
||||
@@ -5,8 +5,8 @@ ii. leg limits are checked when entering spread orders
|
||||
|
||||
i:
|
||||
|
||||
1. Pick a 2 legged spread (lets say SIU8-SIZ8). Set the clip limits high so that they dont interfare.
|
||||
Set the product position limits high as well so they dont interfare either.
|
||||
1. Pick a 2 legged spread (lets say SIU8-SIZ8). Set the clip limits high so that they don't interfere.
|
||||
Set the product position limits high as well so they don't interfere either.
|
||||
|
||||
2. For the security limits (which is what we will be testing), we want Max Long and Max Short of 20 and 30
|
||||
for the SI futures and 100 and 110 for the SI spreads respectively.
|
||||
@@ -26,4 +26,4 @@ ii:
|
||||
6. Enter a 15 lot buy for SIU8. Any spread buy order of > 5 should be rejected, since this will violate the 20 long limit.
|
||||
|
||||
8. Enter a 20 sell for SIZ8. Any spread buy order of > 10 should be rejected since it will
|
||||
violate the 30 short limit.
|
||||
violate the 30 short limit.
|
||||
@@ -1,19 +1,19 @@
|
||||
This test verifies that users and accounts can be de activated which
|
||||
This test verifies that users and accounts can be de activated which
|
||||
|
||||
1. Pick a future, lets say SIU8.
|
||||
|
||||
2. Enter an order and verify that it goes in.
|
||||
|
||||
3. In the risk admin, select your logged in user, uncheck "Is Active" and save.
|
||||
3. In the AdminUI, select your logged in user, uncheck "Is Active" and save.
|
||||
|
||||
4. Now enter an order again, verify that its rejected and that the rejection message
|
||||
makes sense.
|
||||
|
||||
5. Do the same for the account (ie in the risk admin, go to the account selected in the
|
||||
5. Do the same for the account (i.e. in the AdminUI, go to the account selected in the
|
||||
ladder dropdown and uncheck "Is Active").
|
||||
|
||||
6. Verify that orders going into that account are rejected and that the rejection message
|
||||
is clear.
|
||||
|
||||
7. Verify that the account's "Is Active" is correctly applying to that account only, ie you
|
||||
can still enter orders into other accounts
|
||||
7. Verify that the account's "Is Active" is correctly applying to that account only, i.e. you
|
||||
can still enter orders into other accounts
|
||||
@@ -1,11 +1,11 @@
|
||||
This test verifies that users can be created and their passwords can be changed
|
||||
|
||||
1. Log on to the risk admin. Go to the users tab on the left. This will display the users. Select the user you normally
|
||||
1. Log on to the AdminUI. Go to the users tab on the left. This will display the users. Select the user you normally
|
||||
log in the shell with. Change the password (and remember it)
|
||||
|
||||
2. Now start the shell, and make sure you can log in with the changed password.
|
||||
|
||||
3. In the risk admin, click on the add sign and add a new user. Make sure that it shows up there.
|
||||
3. In the AdminUI, click on the add sign and add a new user. Make sure that it shows up there.
|
||||
|
||||
4. Now relaunch the shell and make sure you can log in with the new user (and the password you entered in 3)
|
||||
|
||||
@@ -15,6 +15,6 @@ log in the shell with. Change the password (and remember it)
|
||||
|
||||
-----------------------------------------------------------
|
||||
|
||||
7. Go the main account tab, add an account and make sure it shows up in the risk admin.
|
||||
7. Go the main account tab, add an account and make sure it shows up in the AdminUI.
|
||||
|
||||
b. Associate the user you usually use with this account and make sure it shows up in the account dropdown in the ladder.
|
||||
b. Associate the user you usually use with this account and make sure it shows up in the account dropdown in the ladder.
|
||||
Reference in new issue
Block a user