Input vs. Output Tabs, Abtract Class/Interface/Object Handling

From DevRiot for .Net and Java

Input Vs. Output

So far we have talked about features that are common to input and expected output state tabs. In this section we are going to explain the difference between them.

The main difference, if not the only, resides in the context menu. Right-clicking a leaf node, with integer type, will cause DevRiot's context menu to have three extra items: a combo box and two text fields (like the image below left). The combo box will hold a number of assertions the user can combine with the contents of the text fields to verify the behavior of M.U.T in different ways.

Or you can see a short video(swf) that summarizes what we have covered so far [1]

Abstract Class/Interface/Object Handling

Because of the nature of these types DevRiot will ask the user extra information through a new dialog (above left). In this dialog the user can provide the type that will replace the original type. Some things to note:

• Full names are required (namespace + type name).
• Generic types, array types can be used where applicable (i.e substituting an object for integer array).
• The context menu will provide ways to handle these cases (image above right).