Please can someone help me out with this technical test please would really appreciat
Customers are able to enter their personal* and vehicle details on a website. When the customer submits their application, we send the customer details to Experian and we are given a credit score for that customer. Based on their credit score, we will provide the customer with a quote which will use the APR specified for that particular tier.
*Including their postcode which is used to determine whether to apply the 2% APR uplift
A change is being made to the current system to split the existing tier 1 customers into 3 smaller groups (1A, 1B, and 1C). The credit score bands and APR’s for tier 2 and 3 customers remain the same.
Tier 1 2 3
Credit Score Band 880-965 /750-879 / 700-749
APR 22.90% /32.21% /43.17%
Adjustment (Scottish) plus 2% plus /2% plus 2% to ARR
FigA - As is
Tier 1A 1B 1C 2 3
Credit Score Band 965+ /923-964 /880-922 /750-879 /700-749
APR 16.0% /20.90% /27.40% /32.21% /41.72%
Adjustment (Scottish) plus 2% /plus 2% /plus 2% /plus 2% /plus 2% to ARR
Fig B – To Be
REQ001 – Split existing tier 1 product to tier 1A, 1B and 1C based on the credit scores bands shown in Fig B
REQ002 – Apply the APR specified in Fig B to quotes generated for tier 1A, 1B and 1C customers
Using Excel, write a series of tests that will verify the implementation of requirements 001 and 002.
Note any assumptions you make or questions you have regarding the requirements.
Imagine a similar scenario to the above, but where the tier is split into six tiers rather than three, and we have a different APR for each county (circa 50 counties). Due to a tight deadline, it is not possible to test every eventuality. Briefly describe how you would decide which tests you would run in this scenario and why.
I'm sure someone will come along and have a go at all the answers for you, but in the meantime what is your initial answer to the two tasks?
(Have you checked out boundary value analysis and equivalence partitioning?)
Last edited by meridian_05; 05-17-2016 at 11:08 AM.
Task 1, use boundry analysis as the previous poster said. Also, don't limit yourself at just the credit score boundries, you want to look at data type boundries as well.
Task 2, you can first use a K-map to simplify the logic testing space, or you can use orthogonal pairs (or a variant called pairwise testing) to narrow down the country combinations.
I'd also question what "Scottish" means, and ask for the developer's source list to investigate whether there are any outliers there. And to flip that around, what does non-Scottish mean - mainland GB excl Scotland, or does it also include Channel Islands, IoM, Norn Iron, etc?
What's returned to the user if they don't have an Experian score?
Are there any assessments based on age? What if a user is under 18, or over, say, 65 (relevant for long term loans such as mortgages, but perhaps not so relevant here based on the interest rates)
Do Experian have any scores outside of those ranges? Does their API return non-integer values or is it possible to do so?
Also, for pairwise test coverage check out https://hexawise.com/. But the key words they're looking for here are "risk based testing".
scottish probably means additional 2% charge on anyone with home address in Scotland.
That's what the result is, but initially the OP would need to question what "home address in Scotland" means to the requirements, and how that has been implemented in the system.
Originally Posted by tottallyoff
For example, does "Scottish" mean anyone with a postcode in mainland Scotland? Or council areas? Are offshore islands included or excluded? If postcodes, are they determined via a lookup list hardcoded by the developers, or does the application go back through an API to Royal Mail? Are there any outliers on the borders where a user might have a Scotland postcode but an English council (TD in Galashiels, for example, where some postcodes are run by Scottish Borders Council and a handful by both Scottish and Northumberland or Carlisle Councils)?
I totally agree, validating address is very important. I dealt with foreign customer in one of my previous project and postcode validation was a issue.