Just set the new field attribute “OLEMarkerField” to the reference name of a work item field that should store these meta information. Now WordToTFS can detect those embedded OLE-objects and store that information into a separate work item field. There are different reasons for this desire that reach from administrative tasks to review of those objects. In some cases users want to know whether a work item contains OLE objects. Whenever a user integrates OLE-objects in an HTML-backed field of a work item, some magic is done behind the scene (more information on the OLE support can be found in the user guide at pp. Especially the attribute “ResolveResolutionState”, which is yellow highlighted, is very important to get a meaningful resolution state instead of an internal id number.įigure 4: WordToTFS Configuration for analysis information of Test Run OLE-objects

The following excerpt of the WordToTFS configuration (see figure 4) shows what needs to be added to the WordToTFS-configuration. Failure Type and Resolution of a particular Test Run (see figure 3).įigure 3: Change analysis information of a Test Run Such an area was the analysis information that can be used to document e.g. Nevertheless, there is some data, that has not been that easy to export or it was even impossible. It is possible to include a lot of information into the Test Result Report. Since we want to support both scenarios, a new attribute in the configuration can be used to control this behavior (see figure 2).įigure 2: New attribute for Test Result Reports Test Result Report includes Analysis information However, there are scenarios with the requirement to also show Test Case 3 in the Test Result Report, even if it has never been run.įigure 1: Test Specification and Test Result Report In the sample in figure 1, the Test Result Report would contain every test case from the Test Specification but not Test Case 3.

After some test cases have been executed, the Test Result Report contains those test cases, that have been executed. By creating a Test Specification with WordToTFS, the document might contain the structure shown in figure 1 – “Test Specification”. A very simple Test Plan contains some test suites and test cases. To explain this in detail, the following scenario is used. Due to regulatory requirements, we extended the test result reports so that not only test cases with results are exported into the document. With the existing functionality users can create separate test documents: Test Specifications and Test Result Reports. Test Result Report including Test Cases without results Some major improvements are made in the area of test reports. Test Specifications and Test Result Reports Please find more details on this topic at the end of the post. Basically both versions have the same features, but WordToTFS 5.3 still works on the Visual Studio 2015 API while WordToTFS 6.0 is one step ahead using the Visual Studio 2017 API. There are a lot of new features and also some bug fixes we’re going to explain in this blog post. We are proud to announce the new release of WordToTFS that has been sim-shipped with Visual Studio 2017.

Glyphr studio version 5.3