Channels ▼
RSS

Tools

Achieve More Comprehensive Verification With Less Work


Adopting Loosely Coupled Comprehensive Verification

Although Verification Manager itself can be used without change, adopting Loosely Coupled Comprehensive Verification requires more work and more invasive changes than the other subsystems. The first and most critical step is to define the interface between test cases and Verification. The methods that make up this interface can be of any scope and organized in any fashion you like, but each Begin/End pair must enclose a well-defined set of actions whose consequences can be reliably predicted from the input parameters. This can be a difficult task at first, but it is ultimately a rewarding one.

Once your interface is defined you can stub out the methods on the Verification side and then modify your test cases to call the Begin and End methods at the appropriate locations.

Finally, move the expected state data generation from your test cases into the various Expected State Generators. In many cases you will be able to simply remove the post-action state verification from your test cases, but at times you will need to augment the built-in state comparators to handle data types specific to your application.

--M.J.H.

Back to Article


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.