CaseComplete Cumulative Release Notes

Current Version: Professional, version 15.0
June 2020

Installation

After downloading, select the Run option in your browser to start the installation process, or double click on the CaseCompleteSetup file.

Upgrades

When upgrading to a new version of CaseComplete, your previous version will not be uninstalled or overwritten. Both versions will be available, allowing you to evaluate the new version without disturbing your existing environment. Use the Windows control panel to uninstall the previous version when you no longer want it.

If you have an active 1-year support agreement, you can use your existing serial number to activate the new version (learn how to find your serial number). To determine if your serial number qualifies for a free upgrade enter your serial number on this page. If not, you'll need to purchase an upgrade.

The project file format has not changed from the previous version (Professional 14). File compatibility summary:

• Backward compatibility: This version can open projects from any previous version.
• Forward compatibility: Professional version 13 and later can open projects saved with this version.
  Versions 2015 - 2017 can open projects saved with this version but will issue a compatibility warning.
  Versions prior to 2015 will not be able to open projects saved with this version.
• Shared Project compatibility: Starting with Version 14, older version control systems that rely on MSSCCI are no longer supported. More information.

System Requirements

• Windows 10, Windows 8.1
• Microsoft .NET Framework version 4.5
• Microsoft Office 2007 or later (to take advantage of Word and Excel reporting)
• PDF viewer to read the tutorial

Version 15.0, June 2020

File Compatibility

The project file format has not changed from the previous version (Professional 14).

• Backward compatibility: This version can open projects from any previous version.
• Forward compatibility: Professional version 13 and later can open projects saved with this version.
  Versions 2015 - 2017 can open projects saved with this version but will issue a compatibility warning.
  Versions prior to version 2015 will not be able to open projects saved with this version.

Enhancements/Features

• New mutliple-choice field type for custom fields: allows users to select one or more values from the choice list
• New options for Jira upload: include the item ID in the name, or an item's notes in the description
• Excel import
  • Support importing sub items (notes, issues, etc.)
  • Support importing from multiple sheets
  • New keyword to specify the kind of items being imported (no longer need to select it on the import form)
  • Please click the Help button on the import form for the expected file format
• Show primary and supporting actors in the Use Case and Project Specification Word reports
• Clean up Connect tab: rename TFS to Azure DevOps; add Stories to the export to Excel submenu; move HP Quality Center buttons to the Excel submenu
• Suport Windows authentication when accessing a Subversion Server project
• Detect file corruptions when saving to prevent overwriting the last valid save
• Show a visual indication on the prose tab of the use case details form when when prose exists for the flow of events
• New installer: faster installs, simpler command-line installation
• Add Turkish spelling dictionary

Defects Fixed

See the Professional 14 release history for fixes made since the original release of Professional 14. Those fixes, along with the following, have been fixed in version 15.0:

• Diagram should be brought to foreground when navigating to it from a details form
• Opening the dynamic help in a details form sometimes shows help for the wrong tab
• The diagram tab in the use case details form is missing dynamic help
• Error when using an uninitialized $$variable in a where clause or $if statement of a report
• Should ask for confirmation when deleting a project item from a diagram
• A new item is sometimes shown in the wrong order relative to its siblings in the project browser
• Fix inconsistencies and readability issues in several item detail forms
• Jira error when attempting to convert a sub-task back to its original type (should leave it as a sub-task)

Known Issues

• Pasting large images into test step cells can result in out-of-memory exception.
• Tables are not supported in rich text fields.

Version 14.0, May 2019

File Compatibility

The project file format has not changed from the previous version (Professional 13).

• Backward compatibility: This version can open projects from any previous version.
• Forward compatibility: Professional version 13 can open projects saved with this version.
  Versions 2015 - 2017 can open projects saved with this version but will issue a compatibility warning.
  Versions prior to version 2015 will not be able to open projects saved with this version.

Important: Older version control systems that rely on MSSCCI are no longer supported starting in version 14. This includes SourceSafe and TFS via the MSSCCI provider (instead, TFS, a.k.a. Azure DevOps, is now supported natively). Upon opening a project that uses an unsupported version control system, you'll receive a warning, but you can continue using the project without version control. To share it to a new version control system, perform a File / Save As, followed by a File / Sharing / Share this project.

Enhancements/Features

• New feature: project templates - create templates that you can use as a basis for new projects
• TFS upload
  • Support uploading of use cases
  • Upload diagrams and related images as attachments
  • Upload item properties and custom fields as tags
  • Store the unique ID in a comment instead of in the item's description
• Shared projects
  • Distinguish between new, deleted, and changed files in the check-in and undo checkout dialogs
  • New and deleted files can be "undone" via the undo checkout dialog
  • Sharing Settings dialog now offers option to completely remove version control settings from a project
  • Improved performance
• Diagramming
  • Lock a shape's position. This lets you drag-select foreground shapes without moving the background shape. For example, you could lock the background Window shape in a UI mockup.
  • Added a hand cursor shape to the UI shapes library
  • When creating a new diagram from the ribbon button, set the default owner to the selected item
  • Added a transparent option to the shape's fill color dropdown menu
• Word Reporting
  • Large diagrams are now split across multiple pages. You can control the size at which the diagram is split with new keywords, $DiagramSplitH, $DiagramSplitW
  • New builit-in variable, $$Empty
  • New keywords, $Project and $TopLevelPackage, that display the project name, and the name of the top-most package an item is a descendent of, respectively
• Added a Create Definition button to the Home tab. Removed Create Activity Diagram button (but still available via context menu).

Defects Fixed

See the Professional 13 release history for fixes made since the original release of Professional 13. Those fixes, along with the following, have been fixed in version 14.0:

• Options in the filter tab are sometimes truncated when the display scale is set to 125%
• The color picker dropdown buttons on the ribbon don't show all choices the first time selected
• Stories and Definitions are missing in the modified section of the show changes report
• Referenced requirements should be sorted by ID in the Use Case and Project Specification Word reports
• The export picture dialog for a diagram is using the incorrect bounds to start

Known Issues

• Pasting large images into test step cells can result in out-of-memory exception.
• Tables are not supported in rich text fields.

Version 13.0, April 19, 2018

File Compatibility

The project file format has changed from the previous version (2017) to store custom fields for issues. If you use an older version of CaseComplete to open a project saved with this version, you'll receive a compatibility warning. You will be allowed to open and edit the project, however custom fields for issues, if any, will be unavailable. For this reason, everyone on your team should upgrade at the same time, especially if you share projects.

• Backward compatibility: This version can open projects from any previous version.
• Forward compatibility: Versions 2015 - 2017 can open projects saved with this version but will issue a compatibility warning because custom fields on issues will be unavailable.
  Versions prior to version 2015 will not be able to open projects saved with this version.

Enhancements/Features

• Items can be flagged, for example to mark frequently viewed items. Each user has their own set of flagged items.
• Custom fields are now supported on Issues
• New items can be created directly from the item details form
• Filtering based on existence of child items. For example, Use Cases where issues exist; Actors where goals don't exist, etc.
• Option to show IDs in the project browser
• Customizations made to the diagram shapes library are now saved between sessions. For example, if you choose to reorder or hide shape libraries, those changes will be in place the next time you start.
• Spell checking options to ignore upper case words, and ignore incorrect sentence capitalization
• Improved search results:
  • Tooltip shows full path of matching item
  • Can select the owner of child items (such as notes) in the list and project browser
  • Item ID of owning item are shown in location column
• Scroll position of the project browser is saved between sessions. The expanded state of items is also saved (already available in 2017).
• When uploading CaseComplete issues to Jira, if a custom field named Summary exists, it will be used for Jira's summary field instead of the issue's description

Defects Fixed

See the 2017 release history for fixes made since the original release of 2017. Those fixes, along with the following, have been fixed in version 13.0:

• After adding a new actor or definition, hyperlink formatting isn't shown for the item when it appears in existing text
• Changes made in the description tab not saved after navigating to a new package using the package location bar

Known Issues

• Pasting large images into test step cells can result in out-of-memory exception.
• Tables are not supported in rich text fields.

Version 2017

Data File Compatibility

The project file format is unchanged from the previous version.

• Backward compatibility: This version can open projects from any previous version.
• Forward compatibility: Version 2015 can open 2017 projects. Versions prior to version 2015 will not be able to open projects saved with version 2017.

Enhancements/Features

• Upload user stories to Microsoft TFS, including Visual Studio Online.

• Increase Font button now gets applied to more locations, including all item forms. Works with new keyboard shortcuts, Ctrl + and Ctrl -.
• Ctrl+0 keyboard shortcut resets diagram zoom to 100%.
• Double click on note in a filtered list tab opens the details form of the owning item, and selects the note.
• Allow a new project name when using Save As.
• (Shared projects only) Don't require SHIFT key to reveal Run Cleanup.
• Added ability to duplicate dictionary definition fields.

• Reporting language improvements (don't require spaces around comparison operator, add explanation to invalid property error).

Defects Fixed

See the 2016 release history for fixes made since the original release of 2016. Those fixes, along with the following, have been fixed in version 2017:

• Exception importing from Excel when Parent ID contains only a space.
• The Dictionary was not rendering properly on the HTML Complete Report - Grouped by Item Kind, Full Description.

Known Issues

• Pasting large images into test step cells can result in out-of-memory exception.
• Tables are not supported in rich text fields.

Version 2016

Data File Compatibility

The project file format is unchanged from the previous version.

• Backward compatibility: This version can open projects from any previous version.
• Forward compatibility: Version 2015 can open 2016 projects. Versions prior to version 2015 will not be able to open projects saved with version 2016.

Enhancements/Features

• Your project now gets saved automatically every 5 minutes by default. This replaces the autosave behavior which saved backup files that required manual recovery when disaster struck.
• We made renumbering IDs easier. In the renumber IDs dialog, you can see ID prefix conflicts and what the results of the renumbering will be before kicking off the renumbering operation.
• The issues dialog now lets you navigate to the next and previous issues in the list, as well as open the item that owns the issue. Also the form is now sizable and will remember its size and location.
• We added more safeguards to detect and prevent errors when joining and creating shared projects.
• Now you can choose a destination package when importing items from Excel.
• We changed the default orientation for new diagrams to landscape. Prefer portrait? There's now a setting in the options dialog letting you choose a default.
• We greatly simplified the Save As dialog. Instead of a complex two-step process, just specify the destination folder and you're good to go.
• To make it easier to tell which project is which, the path of the project is now displayed on its start page tile.

Word and Excel Reports

• New keywords:
  • $NestLevel: How many levels deep an item is nested.
  • ReferencedDiagrams: Lists referenced diagrams for items other than test steps and flow of events
• Changed $indent to support any nestable item (use cases, requirements, etc.), not just steps.
• Can now report test scenarios in the context of a package. Use this when you want to show all test scenarios owned by use cases and requirements in a given package.
• A blank line is no longer necessary between $list and $end keywords.

Defects Fixed

See the 2015 release history for fixes made since the original release of 2015. Those fixes, along with the following, have been fixed in version 2016:

• Adding a carriage return to an item in a diagram can result in the item's name being truncated or completely lost when viewed in the item's details form.
• When underlining a word that has been highlighted using double click, the trailing space gets underlined too.
• The grid for definition fields (very annoyingly) scrolls horizontally while tabbing between columns when the vertical scrollbar is present.
• When a definition field's type is set to another definition, it's not color coded as a definition.
• Scrolling using the mouse wheel doesn't work in the flow of events (a problem in Windows 10 only).
• Certain characters should be disallowed in the package prefix because they cause problems when detecting ID links.
• Certain characters should be disallowed in custom field names because they can't be used in word reports.
• Word prevents generating a report from a template that was saved from an email attachment, but the resulting error is confusing. Display a more helpful message instead.
• A "where" that's part of an item's description can cause a report to fail under certain circumstances because CC thinks it's part of a where clause.
• Exporting requirements to Quality Center via Excel doesn't use the correct parent path for child requirements so they don't get imported into QC correctly.
• Should automatically detect when a license is back in compliance after it gets cleared on the activation server.
• (Shared projects only) Could incorrectly report that a user has insufficient permission when accessing a shared project.
• Activity diagram: the step number in the "continue at" shape wraps if it's a substep. Success guarantees can overwrite the last step.
• Performing a renumber IDs on a package that doesn't result in any changed IDs leads to a "can't save a read-only file" error if package isn't checked out.

Known Issues

• Pasting large images into test step cells can result in out-of-memory exception
• Tables are not supported in rich text fields

Version 2015

Data File Compatibility

Both the data file and diagram file formats have undergone a major change from the previous version.

• Backward compatibility: This version can load projects and diagrams from any previous version of CaseComplete.
• Forward compatibility: Versions prior to version 2015 will not be able to load projects or diagrams saved with version 2015.

Enhancements/Features

• Upload your projects to Jira
• An activity diagram is always available in the use case details dialog without having to generate one
• Enhanced autocomplete makes it easier to enter common terms and references to other items
• Nest your user stories and use cases to help keep them organized
• More easily nest and unnest items using new arrow buttons above the project browser
• A new traceability tab has been added to all details dialogs that shows all referenced and referencing items
• The dialog to add referenced requirements has been improved to make it easier to find related requirements

Word and Excel Reports

• New keywords:
  • $InstantDiagram: display the auto-generated activity diagram for a use case
  • ReferencedItems and ReferencingItems: report references of any kind of item
  • New reference type, ByName, available for filtering references (in addition to existing Explicit and IDLink types), e.g.

      $listReferencedActors where RefType = ByName

  • $repeatDefinitions replaces $repeatDictionary, which has been deprecated (still supported, but please transition to the new keyword)
  • $repeatReferencedDefinitions replaces $repeatDomainObjects (deprecated)
    • Besides the name change, it now works in the top level context so you can report on only the definitions that are referenced by the items being reported on
• The built-in reports for Use Cases and the Project Specification now show auto-generated activity diagrams. This will cause double reporting of activity diagrams for use cases that already have a generated activity diagram. To prevent this, you have several options listed below.
• Enhancements to the Referencing keywords (e.g. ReferencingUseCases, etc.):
  • Allow generation of the same information that's shown in the new Traceability tab
  • Now work in all contexts, not just for definitions and requirements
  • Can be filtered using the where clause, e.g.

      $listReferencingActors where RefLocation = Goal

  • Retrieve all references, whether they're by id, by name, or explicit

Miscellaneous

• Updated the look and layout of many dialogs
• Updated the look of all tooltips
• The last tab you were viewing will be the default tab the next time you start CaseComplete
• The default search option has changed to search everything
• When opening the help pane in a details dialog, the dialog expands if necessary
• Stories can be exported to MS Project
• Pasting a large block of text no longer causes flashing in the editor
• Added Czech spelling dictionary
• Padding added to activity diagram shapes
• Updated diagramming component to latest version

Defects Fixed

See the 2014 R2 release history for fixes made since the original release of 2014 R2. Those fixes, along with the following, have been fixed in version 2015:

• $Parent<AnyValidProperty> doesn't work in the context of a referenced item
• Exception when trying to run a report from the examples folder via the recent reports list
• Unable to specify a default value for story priority
• (Shared projects only) Wording in shared project dialog should state that permissions must be Full Control, not just write access
• Report generator was excluding child requirements when reporting referenced definitions for a package
• The search results list doesn't show the owning package for definitions
• The definition ID isn't shown in the Referenced by tab of the requirements dialog
• Incorrect checkout option given when creating a child requirement
• Exception when generating an Excel report if a $ sign is the last character of a cell
• When typing in a requirement ID, the colored text for the hyperlink is sometimes wrong
• When reporting on selected test scenarios, the selection is ignored and all test scenarios get included
• Child requirements aren't getting exported to MS Project
• When a definition field shows up in the search results, it should display its name, not its description
• After closing the form for a requirement that owns a test scenario, "change test step" gets added to the undo list even though nothing changed.
• Exception when reporting referenced diagrams from a requirement's test scenario
• Vertical scroll bar for help pane should only show when needed
• When duplicating a definition it loses its referenced requirements
• A new item added via quick entry view can get added to wrong package
• The dialog to confirm a checkout can clip long file names
• CaseComplete can hang after a paste when there are many misspelled words under rare circumstances.

Prevent double reporting of activity diagrams

Because the built-in use case and project specification reports now show auto-generated activity diagrams, existing activity diagrams will be shown twice in the generated report: once as part of the regular diagram section, and once as part of the new $InstantDiagram section. To prevent this, you may do one of the following:

• If you want to continue using activity diagrams as you have in previous releases, Customize the built-in template and take out the $InstantDiagram section
• If you haven't made modifications to your activity diagrams that you need to keep, and don't need them uploaded to Requirements.cc or Jira, you can delete them
• If you need to keep your activity diagrams for any reason, e.g. you want them uploaded to Requirements.cc or Jira, customize the built-in template and add a condition that excludes either the existing activity diagrams or the InstantDiagrams as in the following examples.
  
  To exclude your existing activity diagrams and show the InstantDiagrams instead, add a where clause after repeatDiagrams:

    $repeatDiagrams where DgrmType != Activity

  Alternatively, to exclude the InstantDiagram when a generated diagram already exists, add the following around the instant diagram section:

    $set $$HasActivity false
    $whenDiagrams where DgrmType == Activity
    $set $$HasActivity true
    $endwhenDiagrams
    $if $$HasActivity = false
              (Instant diagram section here)
    $endif
  

Known Issues

• Pasting large images into test step cells can result in out-of-memory exception
• Tables are not supported in rich text fields

Version 2014 R2

Data File Compatibility

The data file format remains unchanged from the previous version, however we updated the version control component used for shared projects. If you're not using the shared project feature, or if you use a 3rd-party version control system such as TFS, this has no implications. However, if you're using CaseComplete's built-in file sharing (Subversion), this means:

• When you open an existing project for the first time you'll be notified that your working folder needs to be upgraded. This won't affect other team members and you can continue to collaborate on the shared project even if they haven't upgraded yet.
• Once a working folder is converted, you can't access the project using the previous version of CaseComplete. If necessary, you can revert to the previous version; you just need to re-join the shared project and specify a different working folder.
• When you create a new shared project, team members who haven't upgraded yet won't be able to join that project.

Besides the working folder format, file compatibility is as follows:

• Backward compatibility: This version can load projects from any previous version of CaseComplete.
• Forward compatibility: Versions prior to version 2014 will not be able to load projects saved with version 2014 R2.

Enhancements/Features

• Support indented bullets via keyboard commands: tab to indent, shift-tab or backspace to remove indent
• (Shared projects only) Upgraded SVN client component from 1.6 to 1.8
• (Shared projects only) Added Steal Lock command

Defects Fixed

• Crash when copying with nothing selected and Word data currently on the clipboard
• Numbered lists don’t show numbering in HTML reports and Requirements.cc
• $listAll doesn't list everything when user chooses to report on a package

Known Issues

• Pasting large images into test step cells can result in out-of-memory exception
• Tables are not supported in rich text fields

Version 2014

Data File Compatibility

The data file format has undergone a major change from the previous version.

• Backward compatibility: This version can load projects from any previous version of CaseComplete.
• Forward compatibility: Versions prior to version 2014 will not be able to load projects saved with version 2014.

Enhancements/Features

Major Features

• Go Agile! Create User Stories as an alternative to Use Cases
• Upload your test scenarios to Microsoft TFS, including Visual Studio Online . Once uploaded, you can record and track your test runs.
• A new look to the start page makes it easier to access the items you use most often
• Programatically access your data via the Requirements.cc API

Word and Excel Reports

• Removed built-in report templates that used Office 2003 format (.doc and .xls files). The reporting engine still supports the older format. Contact support if you need the built-in reports in the old formats.
• Refreshed the look of Word and Excel reports, including a complete overhaul of the Dashboard report
• New list keywords: Stories, ReferencedStories, and AcceptanceCriteria
• More support for reporting referenced items: any Referenced<Kind> keyword will work in the context of Actors, UseCases, Stories, Requirements or Definitions (via DomainObjects keyword).

Miscellaneous

• Updated the UI diagramming shapes to have a Windows 8 look
• When opening a related document that's not checked out, give an option to check it out
• Moved Import/Export buttons from the File backstage area to a new "Connect" tab so they're easier to find and get to
• Removed CCEstimator report
• Refereshed theme for the Introduction to Use Cases PowerPoint presentation
• Added Russian spelling dictionary

Defects Fixed

See the 2013 release history for fixes made since the original release of 2013. Those fixes, along with the following, have been fixed in version 2014:

• Long extension names, preconditions, and success guarantees get clipped in activity diagrams
• Steps editor sometimes scrolls back to the top when editing use cases side by side
• Selected items in a diagram change their outline color to red making it hard to see actual colors
• Can't edit the template of a built-in report from the recent reports list (file not found error)
• The HTML Issues report doesn't show issues for definitions and actors. The report should also show the issue status field.
• When exporting to XML, child elements for definitions such as notes, issues, etc. aren't included
• Inserting an image file into a diagram keeps the file open and locked by the OS
• When duplicating a package saved in its own file, custom field values for items in the package don't get copied
• When duplicating a package saved in its own file that has a definition with a field, get an error message and duplication aborts

Known Issues

• Pasting large images into test step cells can result in out-of-memory exception
• Tables are not supported in rich text fields

Version 2013

Data File Compatibility

The data file format has undergone a minor change from the previous version.

• Backward compatibility: This version can load projects from any previous version of CaseComplete.
• Forward compatibility: Versions 2012 and 2012 R2 will be able to load projects saved with version 2013, but data associated with new features may be lost when saved with those previous versions.

Enhancements/Features

Major Features

• Create filters to narrow down large lists of items to just the ones you're interested in.
  • Filter on any field, including custom fields
  • Filter by named date ranges, e.g. show items where Date Modifed is this week
• Create new tabbed views to display your filtered lists.
• Share your filters with teammates.
• Report on filtered items.
• Specify a filter to use when running commandline reports.
• Have you read this far? Be one of the first five people to tweet "I'm cleaning my requirements with @CaseComplete 2013" and win a CaseComplete micro-fiber cleaning cloth.
• Show Notes, Diagrams and Related Documents in a tabbed view.

Word and Excel Reports

• New keywords, $FilterName and $FilterDescription to show filter information when generating a report of filtered items

Defects Fixed

See the 2012 R2 release history for fixes made since the original release of 2012 R2. Those fixes, along with the following, have been fixed in 2013:

• Fixing references to renumbered IDs mistakenly fixes IDs that are the same as the starting portion of the renumbered ID.

Known Issues

• Excel import requires a name column even when an ID column exists
• Pasting large images into test step cells can result in out-of-memory exception
• Tables are not supported in rich text fields

Version 2012 R2

Data File Compatibility

The data file format has undergone a minor change from the previous version.

• Backward compatibility: This version can load projects from any previous version of CaseComplete.
• Forward compatibility: Version 2012 will be able to load projects saved with version 2012 R2, but data associated with new features may be lost when saved with the previous version.

Enhancements/Features

Major Features

• Collaborate on your project with other stakeholders by publishing it to the cloud. Learn more at Requirements.cc.
• Get new users up to speed quicker with a completely redesigned process page (now called the Roadmap)
• Customize the roadmap if desired, or replace it with one that reflects your organization's work flow
• Share packages that are common to multiple projects more easily with improvements made to package import
• Keep track of broad issues by attaching them to packages, now that packages can own issues

Word and Excel Reports

• Support showing diagrams that are referenced in steps, extensions or test steps
  • Example: $repeatDiagrams within the context of a $repeatSteps displays referenced diagrams found in the step
  • New keyword, $indent, allows you to indent the current paragraph based on the nesting level of the current step
  • New list keywords, ProcedureDiagrams and ExpectedResultsDiagrams to display referenced diagrams in the context of a test step
• Improvements to the Test Cases report and Project Specification report
• New list keyword, Issues (as in $repeatIssues) replaces OpenIssues (deprecated, but still supported)
• New keyword, PackageIssues, to retrieve issues owned directly by the package. The Issues keyword behavior is unchanged (retrieves issues for all items in the package).
• Keywords and other text can now appear on separate lines above a $listInCell keyword and will be treated separately, not as part of the list. For example, can now show an extension and its steps in same cell.
• Can report actors that are referenced in requirement descriptions.

Diagramming

• Text formatting tools are now available on the Drawing Tools ribbon tab for diagrams (no longer need to switch to Home tab to change font characteristics of shapes)
• Added an arrow shape to the Callouts diagramming shapes
• When pasting using the right mouse menu, it now pastes at the location of the mouse click instead of offset from the original location

Miscellaneous

• Support drag/drop of requirements to and from definitions
• Added Undo Checkout button to the Home ribbon tab
• Enhanced print preview
• Remember whether testing procedure grid should be turned on in the use case details forms
• Links for shared project documentation now go to the working in teams section of the online knowledge base
• The default when pasting from external applications is now keep text only (affects first-time installations only)
• Renamed the dictionaries tab to Definitions
• Took out the button to import legacy glossary files. Moved that functionality to the Import Package button (.ucg files are accepted there)
• The Add to Dictionary dialog now selects an appropriate default package. Also fixed sizing problem with the dialog, and gave it a UI refresh.
• Gave the Export to UML dialog a UI refresh
• Use the default browser when opening links on the start page instead of always using Internet Explorer
• Made improvements to the sample project to better highlight test scenario features
• Added Canadian English and Australian English spelling dictionaries. Crikey! Let's have a poutine to celebrate.

Defects Fixed

See the 2012 release history for fixes made since the original release of 2012. Those fixes, along with the following, have been fixed in 2012 R2:

• Next/prev buttons on the test scenario details form don't dismiss the current editor
• Drag/drop operations that create a reference asks to check out files unnecessarily
• Popup list used to insert an id reference can get permanently stuck
• $endShowOnce leaves a blank line in the generated report
• When importing from Excel, a trailing space in a column header name causes that column to be ignored
• When importing from Excel, display helpful message rather than an exception when file is missing the header row
• Inserting a definition or actor in colored text causes the color of subsequent typing to revert to black
• Running a report against the current selection when a package is selected should behave the same as the option to run the report against a chosen package
• When creating a new package, the prefix suggestion can sometimes be a prefix that's already in use
• Changes made to some of the fields in the test scenario details form don't immediately cause a check out of the owning package file
• Name of the definition shows twice in the properties window
• Converting projects to 2012 format can cause package ordering to be lost in some circumstances
• Print command doesn't work for some Windows configurations
• Creation of vision document and context diagram use the old-style check out dialog (non-cancelable)
• Example ID doesn't update as user types package prefix in New Shared Project dialog
• Exceptions can occur when working with an activity diagram if the owning use case has a colon in the name
• When an actor is deleted, packages that own use cases that reference the actor aren't checked out
• Deleting a requirement and its child requirement at the same time can cause exception
• Removing projects from recent list on start page can cause index out of range error under certain circumstances
• The Use Case List Word report opens in compatibility mode
• Export dictionary tries to use old glossary report
• The Open Details context menu item on an issue bullet doesn't work for a new issue that hasn't been commited yet via tab or enter
• When reporting domain objects for a package, the processing takes an exceptionally long time

Known Issues

• Excel import requires a name column even when an ID column exists
• Pasting large images into test step cells can result in out-of-memory exception
• Tables are not supported in rich text fields
• When performing Find / Replace, results do not include Test Procedures or Expected Results contents

Version 2012

Data File Compatibility

The data file format has undergone a major change from the previous version.

• Backward compatibility: This version can load projects from any previous version of CaseComplete.
• Forward compatibility: Versions prior to version 2012 will not be able to load projects saved with version 2012.

Enhancements/Features

Major Features

• Installer supports integration with automated deployment tools for large scale rollouts of installations and upgrades.
  • Silent installer
  • Register/Activate during installation
  • Enable/Disable end-user installation of updates via "Check for Updates"
• Built-in Field Customization
  • Customized field values stored in project
  • Specify customized values as default for new projects
• Test Scenarios
  • Support for any number of test scenarios for use cases, requirements
  • Add related documents, requirements, diagrams, setup instructions, notes and issues to test scenarios
  • Test scenarios appear in project browser with owning use case / requirement
  • Record pass/fail results as notes
• Dictionary Enhancements
  • Definitions can be added to any package
  • Multiple dictionary packages can be added to project
  • Definitions displayed in project browser
  • New "details" list view for Definitions
  • Display rules for dictionary fields

Defects Fixed

• Undo checkout from top level package takes a long time
• Exception message when closing a diagram while diagram link tooltip is showing
• Combining a package file back into the parent package causes ordering in project browser to be lost
• Exporting to XML reports error if reserved characters are in package names
• Out of range error when generating QC requirements report with long descriptions

Known Issues

• Excel import requires a name column even when an ID column exists
• Pasting large images into test step cells can result in out-of-memory exception
• Tables are not supported in rich text fields

Version 2011

Data File Compatibility

The data file format has not changed from the previous version.

• Backward compatibility: This version can load projects from any previous version of CaseComplete.
• Forward compatibility: Version 2010 R2 will be able to load projects saved with version 2011.

(* indicates items introduced in Spring service release)

Enhancements/Features

Major Features

• Major overhaul of licensing making it easier to activate and transfer licenses
• Major overhaul of user interface:
  • More logical layout of functions making it easier to find and discover features
  • Dockable panes: the project browser, properties window, and details tabs along the bottom can be hidden or moved. Shapes library for diagram can be hidden.
  • Quick access to the reports you run most often
  • New package filter UI makes it easier to find a specific package
  • Selecting a package in the project browser will filter the lists to show only items in that package
  • Quick search now finds IDs in addition to names
  • Keyboard accelerators added for common actions
  • Changed wording in the project sharing dialogs making them more understandable
• Option to export diagrams as image files when exporting XML (also available in a 2010 R2 service release)
• New packages are now created as separate files by default *
• Diagramming
  • Using custom actor shapes is easy now. When you drag an actor on a diagram, CaseComplete shows a picklist that lets you pick which actor shape you want. When you add a custom shape library containing actor elements, those new shapes are automatically added to the picklist *
  • A default file name is now generated when you create a new activity diagram *
  • Tool for drawing connectors on diagrams (association, include, reference) "pins" the selected type for one-click connector creation *
• Report Generation - "Headless" custom report generation from a command line (for example, generating reports in scheduled jobs) *

Word and Excel Reports

• New Word report that lists use cases only; Existing Use Case Specification report renamed to Project Specification
• Ability to report on items that appear in a given diagram (e.g. $listUseCases inside a $repeatDiagram loop)
• Ability to report which definitions are referenced by the items in a package (also in 2010 R2 service release)
• Ability to report use cases that are referenced in the text of a definition
• Issues report can be generated for a selected package
• Two new list keywords: AnytimeExtensions and AnytimeExtensionsNoSteps
• Two new properties for requirements: IsTopLevel and IsNested
• New keyword directive to control embedding vs. linking Word documents in RelatedDocuments sections: $EmbedWordDocuments (followed by True, False, or Default)
• Legacy report templates removed due to incompatibility with Word 2010. Legacy reports will be furnished by request
• Repeat loops can include a header section ("show once" section) *
• $when keyword enables conditional sections in reports *
• New keywords for including report descriptions, version in reports; these are now displayed in CaseComplete report generator form *
• Report variables for storing, rendering report data *
• Report parameters let you set report values from CaseComplete report generator form that can be used within the report *

Defects Fixed

• Hyperlink text formatting is continued when adding a new line after a line that ends with an actor or definition, and when adding text immediately after a definition
• If a requirement starts with an actor name, sometimes actor hyperlink formatting is applied to the entire requirement name when inserting an ID link to the requirement
• Excel matrix report fails when a requirement contains a $ in the name
• Exception when choosing "select in list" for a nested requirement in the search results window
• Can get exception when generating a Word report that has a $repeat immediately after a page break
• Can get application busy error when generating a Word report that has a lot of spelling and grammar errors
• Don't allow running reports from the .svn folder, or report templates that have non-standard extensions
• $listNotes by itself (i.e. not followed by $Description) throws exception when it appears as the last item in a table cell
• Strip leading and trailing spaces from IDs when importing from Excel
• Requirements referenced from a dictionary element appear empty in reports
• Putting a colon in activity diagram filename fails without letting user know that anything is wrong
• Requirements Word report should sort by ID
• List flickers after changing the value of the current "group by" property for multiple items
• Currently selected items should remain visible after any sort or group of the main list
• Duplicating a diagram causes the diagram to get checked out, not the owning package
• Some help topics missing in dictionary form
• "cc://" URL does not properly launch CaseComplete from a Firefox browser *
• Save As doesn't copy related documents to target folder *
• Error message when duplicating a diagram containing an apostrophe in the name *
• TAB key does not advance cursor to next column when adding an issue in the Actor form *
• "Test Cases" report runs slowly *

Known Issues

• Spacing is incorrect in diagramming tutorial if your computer is set to display at 120 DPI
• If you paste rich text into CaseComplete, not all rich text formatting can be rendered in HTML reports, e.g. images
• Tables not supported in rich text

Contact Info

Please send problem reports and suggestions to:

casecomplete.com