Files
spark/testing/manual/settings/UserSettingsTest.txt
T

116 lines
6.6 KiB
Plaintext

User Settings Test (15 min)
NOTES:
- in addition to the notes below, there is a "Reference" section at the bottom of the test,
feel free to add things to it if you run into problems; impart your wisdom unto the next tester.
- the settings button is located in the bottom-left corner of the Ladder
- the "Default" tab will be referred to as [DTab], "Custom" as [CTab]
- the "Use Defaults" checkbox is located at the top of the dialog
- when "Use Defaults" is checked, [CTab] is disabled ([DTab], however, is always enabled)
- to Import/Export settings to files, click the hamburger icon in the upper-right corner of the settings dialog.
- you cannot open multiple settings dialog for the same Ladder
i) if a settings dialog is already open, clicking the settings button in the Ladder again closes said dialog, then opens a new one
- the settings dialogs do not live update
i) this only pertains to [DTab], as Custom settings are not shared.
- commit changes by clicking "Apply" or "OK"
i) the only difference between the 2 buttons is that "OK" also closes the dialog
- when you commit changes:
i) even if "Use Defaults" is NOT checked, the settings in [DTab] will be compared with the current defaults,
if they are different, the default changes will be committed as well.
ii) be advised of the following scenario:
You have 2 settings dialogs open (call them [A] and [B]), and commit changes to the defaults in [A].
As the dialogs do NOT live update, [B] will have stale defaults.
When you click commit in [B] (even if you have not actually changed anything in [DTab])
the stale defaults in [B] will be committed, effectively overwritting the changes to the defaults you just committed from [A].
- the "sample" areas should always reflect the properties in your editor, if this is unclear, see the reference section at the bottom for a more detailed explanation.
- when the test directs you to "Visually Confirm blah...," just give it a quick glance, if something isn't matching it should be obvious.
- when the test directs you to repeat a step for each property, here is the list (in case it isn't clear in the dialog):
Note: the Sample column is purely output, don't bother clicking it
- Order Badge Style
- Alternate Order Quantity
- Size Presets (aka Number Pad buttons)
- Fonts and Colors section:
for each column (Orders, Bid, Price, Ask, Last)
i) background
ii) foreground
iii) font (family, size, and weight)
- Market Break Lines section:
i) for each "price-line" (session high, ask, mid, bid, and session low)
a) toggle show/hide
b) color
ii) for session range (this is not actually a line, but the color between the session low/high
a) toggle show/hide
b) color
- when the test advises you to name files (screenshots, or ladder settings files), it is because they will be referenced later by that name.
- if you uncheck all 3 market break lines, the ladder resolves to show the bid line by design.
- just to reiterate: there is a REFERENCE section at the bottom, please consult it before getting frustrated, if things are still unclear, ask John.
------------TEST STEPS------------------
1) Launch 2 Ladders of the same Security
- the security needs a few working orders on both sides, and a gap of 5-8 ticks between the top bid/ask.
The gap is needed to separate the market break lines (Bid, Ask, and Mid).
- from hence forth, the 2 ladders will be referred to as "[A]" and "[B]" and their settings dialogs as "dialog[A]" and "dialog[B]"
- at the risk of sounding redundant, the "Default" tab will be referred to as [DTab], the "Custom" as [CTab]
2) Open the settings dialogs for [A] and [B]
3) Make sure that both [A] and [B] are using default settings, then close [B]dialog
4) In dialog[A] (with [DTab] selected, [CTab] should be disabled anyways), change each property, then click "Apply"
5) Visually confirm that all the changes have been applied to both ladders
- the row height should adjust to fit the largest font size,
- the scroll position should be maintained, assuming the AutoRecenterTimer didn't move it.
6) Take a screenshot, name it "A-1-confirmation.png"
7) In dialog[A], export the default settings to a file, name it "A-1.ladder" (instructions on how to import/export are in the NOTES section)
8) In dialog[A], click "Restore to Factory," then click "Apply"
9) Visually confirm that dialog[A], and both ladders, each changed appearance, and match one another.
10) In dialog[A], uncheck "Use Defaults", then select [CTab]
11) Import "A-1.ladder" to Custom, then click Apply
12) Visually confirm that:
- dialog[A] and [A] changed appearance, and look just like they did in "A-1-confirmation.png"
- [B] did not change appearance
13) Click the settings button in [A] and [B] to get 2 fresh dialogs (dialog[A] should close and reopen)
- in dialog[A], "Use Default" should be false, and [CTab] selected
- in dialog[B], "Use Default" should be true, and [DTab] selected ([CTab] should be disabled)
14) Take a screenshot, then save the workspace, then restore it
- visually confirm that [A] and [B] look as they did in the screenshot
- repeat step 13
15) In dialog[A], with [CTab] selected, click "Copy from Default"
- [CTab] should now have the same settings as [DTab]
16) Click the settings button in [A] to close and reopen dialog[A]
17) In dialog[A] select [DTab], then click "Copy from Custom"
- [DTab] should now have the same settings as [CTab]
DONE!!!
Reference-----------------------------------------------------------
Alternate Order Quantity:
- you may send an order with this size via a RIGHT CLICK on a price cell
Size Presets:
- aka the number-pad buttons
- click the expander-arrow button next to the "Size Presets" label to modify them
- you control the quantities in the buttons, and the order in which they appear
Market Break Lines (Bid, Ask, Mid, and Session Low/High/Range):
- each row corresponds to one item, and represents a "horizontal price-line" that will be displayed in the ladder (if show is checked, of course)
with the exception of "Session Range," which represents the fill-color between the session low/high lines
- the rows are ordered in the way they [usually]appear in the actual ladder, with the exception of "Session Range"
Note: "the way they appear" is qualified with "usually" because it is possible that the current best bid and/or ask are outside the range of the actual session low/high
- if you check/uncheck the "show" cell in any row, the sample-grid should reflect this by showing/hiding the item