Complete the "Multi-Market Stock Trading Tests" exercise. Instructions are given below.
Instructions and Questions
I. Open up the Sample Plan called “L) Multi-Market Stock Trading [mixed-strength].”
As you open the sample plan, click on the green “Make an Editable Copy” button. Save this editable copy into your folder called "Training Plans - insert your name here".
II. Note a few significant details about the current version of the plan
Before you modify the sample plan please answer these questions:
1) Create a set of 2-way tests with the existing inputs:
A) How many 2-way tests are generated? ____________
B) How many total possible scenarios exist for this System Under Test? ____________
(This information is available by hovering on the (i) icon on the "Create Tests" screen).
C) Using the Matrix Chart, how many 2-way tests are required to achieve coverage of 85% of the Value pairs? ____________
D) Using the Matrix Chart to identify it and list at least one pair of values that gets tested for the first time in test number 50 ____________
2) Create a set of 3-way tests with the existing inputs:
A) How many 3-way tests are generated? ____________
B) How many total possible scenarios exist? ____________
C) Using the Orange Coverage Chart, how many 3-way tests are required to achieve coverage of 50% of the 3-way combinations pairs? ____________ (Remember to select 3-way from the drop down menu on the orange coverage chart)
Now please modify the plan in the following ways (explained in sections III—V):
Senior stakeholders who reviewed these draft test sets are telling us that they want certain Values to appear relatively more often than other Values because the equal weighting strategy currently used seems “wrong” to them. Keep in mind that the stakeholders at this point are not familiar with how Hexawise works or how test optimization works. Therefore, it is not at all clear at this point whether it would be a good idea to “fix” the plans in the way that these stakeholders are asking us to do.
1) Weigh the following "high-priority” Value so that it appears relatively more often than other Values
Make “HK" appear in slightly more than half the tests. If there are 14 Values now for Transaction Exchange (Country) (where one is HK), add HK 13 more times (so 14 Values would be HK and 13 Values would be other countries that are not HK.
A) How many 2-way tests are required now (after giving extra weighting to HK)? ____________
B) Given how many extra tests are required, would you recommend that this weighting strategy be used? ____________ Why or why not? ____________________________________________________________
(Instructions: include the change you made to the test plan and continue (e.g., there should be 14 HK values and 13 "other location" values in the plan now...)
2) Weigh the following “nuisance” Value so that it appears less often than other Values
For “Attempt to Change or Cancel Order Before Fulfilled,” there are two Values (Yes and No). Each time “Yes” appears in a test, it creates a significant amount of extra work for the tester executing that test. So lets see if we can decrease the proportion of tests that have “Yes” for Changes or Cancels (without sacrificing 2-way coverage). Change the Values in this Parameter by adding 2 additional “No” Values. (After your modification, there will be 4 Values in the "Attempt to Change or Cancel Order Before Fulfilled” parameter: 3 will be No; 1 will be Yes.
A) How many 2-way tests are required now (after giving “triple weighting" to the No's? ____________
B) Given how much less effort will be required to execute the tests, would you recommend that this weighting strategy be used? ____________ Why or why not? ____________________________________________________________
(Instructions: include the changes you have made to the test plan and continue (e.g., there should be 14 HK values and 13 "other location" values in the plan, and 3 "do not change or cancel" and 1 "Yes" (change or cancel) now...)
IV. Force some high-priority scenarios to appear
When you create set optimized tests for a complex system, it is always important to ask “what high priority scenarios do we want to make sure get covered?” If there are complex business rules or known problem areas, you should ensure that they appear in your generated tests by using the Requirements feature. Any requirements that will be covered when just 2 Values appear together in a single test case will appear in your tests. But sometimes a requirement or a business rule can only be tested when 3 or more specific Values appear together in a test case; the Requirements feature allows you to easily force such high-priority scenarios to appear in your test sets.
1) Add in this business-rule-driven high-priority scenario and Expected Result using the Requirements feature in Hexawise:
If a Stop Limit Order is placed at a VIP lounge for a security on an Australian exchange and the transaction size is very large, then confirm that a special report should be generated and sent to ASOHS (the Australian Special Order Handling System).
2) Add in this known-problem-area-related high-priority scenario and Expected Result using the Requirements feature:
In the last few months, there have been a few reported issues when new users have tried to sell shares on an Indonesian exchange. Because this is a known issue, confirm that this specific 3-way combination scenario is "forced" into the test scenarios that will be executed.
V. Remove a couple System features from the test set
1) In the next release, functionality will be changed. No “second transactions” will be supported as part of a transaction. Every transaction will involve only a single order. Delete the Parameter called “Second Transaction?” from the plan.
2) In the next release, the firm (for business reasons never fully communicated to BA’s or Testers) decided to cease operations in Thailand and prohibit transactions on the Thai exchange. Remove Thailand from the list of Values that appears in the Parameter called “Transaction Exchange (Country).”
A) How many 2-way tests are generated at this point? ____________
B) How many pairs of values are in the System Under Test? _________
C) How many total possible scenarios exist at this point? ____________
VI. Make necessary changes to incorporate a regulatory change and feature change
1) Regulatory change: Japanese tax authorities have announced that they need to receive tax statements every time a Transaction size is "greater than 500,000.” Modify your test inputs (if necessary) to force a test for this to appear in your test set.
2) Functional change: all customers issuing Sale orders for some (but not all) of the shares they own will now be prompted to answer the question “Which of your shares would you like to sell?: (a) The shares you bought longest ago, or (b) The shares you bought most recently)." Modify your test inputs (if necessary) to force this feature to appear in your test set. Also, make sure that none of your test scenarios that involve Purchase transactions prompt the user to answer “which of your shares would you like to sell?”)
VII. Document your answers to the questions above in a note in your updated plan and share your plan (in a folder called "Training Plans - insert your name here") with firstname.lastname@example.org by following the instructions located here