Model-Based Testing with Spec ExplorerLearn, discuss, ask questions about Spec Explorer. Spec Explorer is a model-based testing tool that runs as an add-in to Visual Studio. Please participate freely and help us make the Spec Explorer experience even better!
Hello! We are delighted to announce the newest version of Spec Explorer 2010, Release 3.5.
Spec Explorer 2010 Release 3.5 contains new features, improved documentation, plus over 60 bug fixes. Please consult the Release Notes and our Home Page to access this release.
This release contains new / enhanced features including:
· Model change detecting: The model change detecting feature detects all model changes and decides if Spec Explorer needs to re-explore the model. For specific machines, if Spec Explorer detects any change in the model code, cord script files, or other inputs, or detects a tool version change, Spec Explorer will start a new exploration; otherwise, Spec Explorer will use existing exploration result files for current exploration viewing, test code generation, and user customized post processing. The UI has been updated to allow you to force Spec Explorer to re-explore the machines. This feature greatly improves the user experience by preventing unneeded lengthy validation and exploration events, which frequently happened in previous versions.
· Multiple machine processing: Now you can select multiple machines in Exploration Manager and explore, generate test code, or perform post processing tasks on them. For multiple machine processing, Spec Explorer generates a summary including all information of the batch-processing.
· Cord context menu: Spec Explorer adds a new context menu item “Go To Definition” in the Cord editor, which enables users to navigate to specific configurations and machines. This is part of an ongoing effort to improve the Cord editing user experience and the general integration of the tool with Visual Studio.
We hope you enjoy this release and look forward to hearing feedback from the Spec Explorer community.
This forum has been locked; it will still be available for review in the Archived Forums folder. Any future posts on this topic should be put in the Test Tools in Visual Studio 2010 and 2012 forum.












































|