Congratulations!! You have been selected to create a banking simulator. After meeting with the clients, you have agreed on requirements and even have developed a basic design of the program. Basically, the software must be able to create accounts, deposit, withdraw, and transfer funds, and deal with fees, interest, etc. You have decided to embrace Test-Driven Development (TTD) for this project. This means that, now that the requirements and design have been developed, the next step is to design unit tests for all the classes identified in the design. (Normally you might develop the tests at the same time as starting the implementation, but for this project, we are only developing unit tests.) View the UML class diagram for the bank simulation. (You can learn about UML from the class resources.) Requirements: In this project, you will be given a list of classes and their public methods, for a simple (not realistic) banking simulation program. Your group’s task is to create a thorough set of unit tests. In order to run your tests, you will skeleton classes with stub methods; you should not attempt to actually create a banking simulation program! To save time, I have provided a Zip file with the skeleton classes. You should probably add all those, and a package for your unit tests, before your initial commit. Download BankSimSkeleton.zip. Since there is no real code to test (only stub methods), it is expected that all your tests will fail. Keep in mind you are only to create unit tests, not a working program. Naturally a real banking system needs persistent data (CRUD) to hold account data between runs of the program and many other features. Normally you would need to test that functionality as well. To keep this project simple, no persistence classes or methods need to be tested, and are not mentioned in this project’s requirements. No exception handling is included in this project either. In other words, this simulation is not terribly realistic. (As a matter of fact, it is not a great design either!) For a first project where you must create unit tests in a group, it should be complex enough as is. Keep in mind the requirements for testing on financial software is high, so be sure to have sufficient tests for the simulator (and not just a few happy path tests). Note that of the six classes shown, some may not have any methods except trivial ones, and thus do not require any unit tests. Some of the methods shown might be considered trivial by your team; you shouldn’t include tests for those either. Additionally, some methods cannot be tested easily using JUnit, such as methods that display a GUI. Don’t try to test such methods, although some of them are shown in the requirements. Testing such functionality requires advanced tools and techniques, such as GUI testers and a mocking framework (e.g., Mockito). I have also omitted nearly all getters and setters, toString, compareTo, clone, and other such methods from the requirements, but of course a real program must have them as needed. You can actually see those methods in the skeleton classes, for example the Account.getBalance() method. In general, such methods are trivial to implement and do not need unit tests, although it is likely you will need to use getters and possibly setters in your unit test methods. However, if your team feels any of those methods merit a unit test, add appropriate unit tests for them. (It isn’t as if adding additional tests is ever a bad thing, just that often it’s a waste of time.) The Classes to Test: For the initial version, we can find many candidate classes but in the end only a few are needed to meet the requirements for a simple banking simulation. These classes and their more important methods are described below. Note all classes are in the package banking. Take some time to example these classes and their methods. See how they can be used in your tests. For example, to create a SavingsAcccount to test you need to create a C…
Looking for solution of this Assignment?
WHY CHOOSE US?
We deliver quality original papers |
Our experts write quality original papers using academic databases.We dont use AI in our work. We refund your money if AI is detected |
Free revisions |
We offer our clients multiple free revisions just to ensure you get what you want. |
Discounted prices |
All our prices are discounted which makes it affordable to you. Use code FIRST15 to get your discount |
100% originality |
We deliver papers that are written from scratch to deliver 100% originality. Our papers are free from plagiarism and NO similarity.We have ZERO TOLERANCE TO USE OF AI |
On-time delivery |
We will deliver your paper on time even on short notice or short deadline, overnight essay or even an urgent essay |