Abstract: An application with a function for inputting feedback incorporated into it is created and presented with the present embodiment. By this means, feedback about the problems in the running of the application may be obtained efficiently. In addition, an application with a function for inputting feedback about the components that define the operations of the application and a function that maintains a correspondence between the feedback descriptions and the components that are the target of the feedback incorporated into it is created by the present embodiment. By this means, the component in the application that the feedback concerns may easily be determined.

Abstract: An application with a function for inputting feedback incorporated into it is created and presented with the present embodiment. By this means, feedback about the problems in the running of the application may be obtained efficiently. In addition, an application with a function for inputting feedback about the components that define the operations of the application and a function that maintains a correspondence between the feedback descriptions and the components that are the target of the feedback incorporated into it is created by the present embodiment. By this means, the component in the application that the feedback concerns may easily be determined.

Abstract: A technique, system, and computer program for presenting test coverage metrics in a visual programming environment. The information is presented in the same general visual manner in which a visual programmer creates a visual program. A number of alternative presentation styles are defined whereby the visual program is augmented to indicate test coverage status. For example, when displaying connections, one color may be used when displaying a connection to indicate that it has been covered, while a different color is used for connections that were not covered. Or, different line styles (such as solid versus dashed, or different degrees of line thickness) may be used to represent the same information. Alternatively, the test coverage status may be indicated by annotating the graphical representation of the visual program with text (such as “covered” or “not covered”).

Abstract: A method, system, and computer program for presenting runtime performance data for analysis in a visual programming environment. The performance data is presented in substantially the same manner in which a visual programmer creates a visual program. A number of alternative presentation styles are defined whereby the visual program is augmented to indicate performance data. For example, when displaying connections, one color may be used when displaying a connection to indicate it has been executed a relatively high number of times, while a different color (or a different hue of the first color) is used for connections that were executed a relatively low number of times. Or, different line styles may be used (such as different degrees of line thickness, or solid lines compared to lines comprised of dashes of varying length) may be used to represent the same information.

Abstract: A method, system, and computer program for providing test coverage metrics in a visual programming environment. A test coverage model for visual programming is defined, which accounts for the specialized nature of visual programming, and the metrics are based on this model. The metrics are expressed in terms of elements familiar to the visual programmer, as opposed to using source code metrics. In a preferred embodiment, these elements comprise events, actions, connections, and attributes. The code implementing a visual program is instrumented according to this model, and test coverage information is gathered as the instrumented program executes.

Abstract: A method, system, and computer program for providing runtime performance analysis in a visual programming environment. A performance data collection technique for visual programming is defined, which accounts for the specialized nature of visual programming, and the analysis is based on this collected data. The performance data is expressed in terms of elements familiar to the visual programmer, as opposed to using a source code approach. In a preferred embodiment, these elements comprise events, actions, connections, and attributes. The code implementing a visual program is instrumented according to this performance data collection technique, and performance information is gathered as the instrumented program executes. Preferably, the information gathered comprises execution counts and elapsed time per element.