Organizing Test Cases in easyb
Test artifacts can be placed with the main classes in a project or they can be placed outside project in a separate test project.
In the case where test artifacts are to be kept in same project, you can have two separate source folders: One folder is for main classes and the other is for test classes. With this arrangement, you can build only the main classes when a package is needed for deploying on a production server. In the folder structure shown in Figure 4, the production code is in under main folder, and the easyb code is under the test folder.
In the case where test artifacts are the be kept separate, the test artifacts are placed outside the actual application. This approach is useful when you have a suite of applications to test. In such cases, a common test project can be created to test all of the applications. Such an arrangement keeps the test code separate from the application, and promotes code reuse. The test code can be written and maintained by a separate test team without having to deal with the actual application.
In the Figure 5, a common test project is created to test a suite of financial applications. All these applications are tested externally.
The reporting provided by easyb supports BDD and presents test results in a very clean and readable format. Developers can iteratively and incrementally test code using the easyb implementation. Thus, easyb enables an agile path toward successful application development, along with readable documentation.