|
1 | 1 | # Instructions |
2 | 2 |
|
3 | | -Simulate a bank account supporting opening/closing, withdrawals, and deposits |
4 | | -of money. Watch out for concurrent transactions! |
| 3 | +Simulate a bank account supporting opening/closing, withdrawals, and deposits of money. |
| 4 | +Watch out for concurrent transactions! |
5 | 5 |
|
6 | | -A bank account can be accessed in multiple ways. Clients can make |
7 | | -deposits and withdrawals using the internet, mobile phones, etc. Shops |
8 | | -can charge against the account. |
| 6 | +A bank account can be accessed in multiple ways. |
| 7 | +Clients can make deposits and withdrawals using the internet, mobile phones, etc. |
| 8 | +Shops can charge against the account. |
9 | 9 |
|
10 | | -Create an account that can be accessed from multiple threads/processes |
11 | | -(terminology depends on your programming language). |
| 10 | +Create an account that can be accessed from multiple threads/processes (terminology depends on your programming language). |
12 | 11 |
|
13 | | -It should be possible to close an account; operations against a closed |
14 | | -account must fail. |
15 | | - |
16 | | -## Instructions |
17 | | - |
18 | | -Run the test file, and fix each of the errors in turn. When you get the |
19 | | -first test to pass, go to the first pending or skipped test, and make |
20 | | -that pass as well. When all of the tests are passing, feel free to |
21 | | -submit. |
22 | | - |
23 | | -Remember that passing code is just the first step. The goal is to work |
24 | | -towards a solution that is as readable and expressive as you can make |
25 | | -it. |
26 | | - |
27 | | -Have fun! |
| 12 | +It should be possible to close an account; operations against a closed account must fail. |
0 commit comments