You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to have a standard set of test inputs and outputs for each exercise to
make it easier to port them to new languages, as well as to help keep the
exercises in sync.
Most problems you will see are stateless - write a function, give it some inputs, expect a certain output. All exercises listed in the example section in fact follow that pattern (custom-set is a bit more complex, but fundamentally it still fits into that pattern, just with multiple functoins)
You may find that bank-account doesn't fall into that pattern if it is very stateful - create a bank account, do some things to that bank account, check some state of that bank account.
If it looks like the bank-account tests can't fit well with the examples listed, try looking at what happened in #488 and #358 , which were also two very stateful exercises.
(Of course, if you find that bank-account can fit well into the stateless model, then you can ignore everything I've said, no worries!)
We want to have a standard set of test inputs and outputs for each exercise to
make it easier to port them to new languages, as well as to help keep the
exercises in sync.
The Bank Account exercise can be found in the ./exercises/bank-account/ directory.
The step-by-step instructions for how to compile a canonical-data.json file is
described in this section of the contributing guide.
See http://exercism.io/contribute/canonical-data/bank-account for the up-to-date list of
language tracks that have an implementation of the Bank Account exercise.
The tracking issue has more context.
The text was updated successfully, but these errors were encountered: