Channels ▼
RSS

Open Source

Behavior-Driven Development With easyb


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.


Figure 4.

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.


Figure 5.

Conclusion

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.

References

easyb

BDD (wikipedia)

Dan North's "Introducting BDD"


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video