What’s New in VectorCAST 6.1 – Part 2

By: 
Lynda Gaines

March 26, 2013

 

Last week we released VectorCAST 6.1. In What’s New in VectorCAST 6.1 – Part 1, I detailed the improvements we have made in this release for ease of use.

In this post I would like to highlight a group of enhancements that help our customers address common testing challenges. Specifically, VectorCAST 6.1 provides the following enhancements:

MC/DC masking – VectorCAST can perform MC/DC analysis and equivalence pair reporting using MC/DC masking as defined in the FAA CAST Position Paper-6. This is in addition to unique cause MC/DC analysis that was supported previously. This feature is of particular interest to those projects performing DO-178C Level A software certification.

Block coverage – a new Coverage option called "Instrument blocks for statements" results in a smaller foot-print for coverage instrumentation because only the last statement of a contiguous block of statements is instrumented when determining Statement coverage. The intermediate statements are considered covered by inference, but data is not collected for them. As a result, the TESTINSS.DAT files and the instrumented files are smaller. This feature is intended for users who have limited program memory for their application.

Abstract class testing - VectorCAST automatically creates a concrete class for each abstract class found in the source code under test. In the Parameter Tree, the dropdown menu listing the constructors for the class now includes the auto-generated concrete class, prefixed with "vcast_concrete_".

Dynamic stubbing of non-testable functions - allows inlined functions to be stubbed dynamically, on a per testcase basis. The inlines appear in the Parameter Tree grouped by header file, under "Stubbed Subprograms," each with a checkbox similar to stubbed UUT functions under the <<SBF>> node.

Dynamic stubbing of library-system calls - allows system-library calls to be stubbed on a per testcase basis. The library calls appear in the Parameter Tree grouped by header file, under "Stubbed Subprograms," each with a checkbox similar to stubbed UUT functions under the <<SBF>> node.

Integration with RequisitePro – VectorCAST now supports RequisitePro as a subsystem in the Requirements Gateway product, to map requirements to test cases and coverage results. We are excited about these improvements.

While they won't all apply to all customers, the ones that do apply to you will save you some time!

Tags: 
Support