Abstract: A conversion tool enables XPS documents to be automatically converted into the Open XPS format and for Open XPS-formatted documents to be automatically converted into the XPS format. The conversion tool may convert content types, package-level relationships, part-level attributes, and image parts into a format supported by either document format.

Abstract: A conversion tool enables XPS documents to be automatically converted into the Open XPS format and for Open XPS-formatted documents to be automatically converted into the XPS format. The conversion tool may convert content types, package-level relationships, part-level attributes, and image parts into a format supported by either document format.

Abstract: A conversion tool enables XPS documents to be automatically converted into the Open XPS format and for Open XPS-formatted documents to be automatically converted into the XPS format. The conversion tool may convert content types, package-level relationships, part-level attributes, and image parts into a format supported by either document format.

Abstract: Test cases are executed by the software engineering test system. The test cases target software products. Test outputs are generated indicating whether the software engineering test system determined the test cases to have passed or failed. Separately, bug records are stored in a first dataset whose records identify corresponding bugs. Records of the test case executions are stored in a second dataset. Records thereof indicate whether a corresponding test case failed when executed. Such records may have bug identifiers entered by a test engineer and corresponding to bugs identified by the test engineer. The first dataset is parsed to identify records of test runs that have failed, and for each such test run record a bug identifier thereof is identified. Statistics such as failure counts are updated for the bugs found in the test run records.

Abstract: A conversion tool enables XPS documents to be automatically converted into the Open XPS format and for Open XPS-formatted documents to be automatically converted into the XPS format. The conversion tool may convert content types, package-level relationships, part-level attributes, and image parts into a format supported by either document format.

Abstract: A conversion tool enables XPS documents to be automatically converted into the Open XPS format and for Open XPS-formatted documents to be automatically converted into the XPS format. The conversion tool may convert content types, package-level relationships, part-level attributes, and image parts into a format supported by either document format.

Abstract: Subject matter described herein is directed to providing font-rendering information (e.g., XPS file) that is usable to print a document. For example, a font file is received that defines a font type included in the document. A determination is made that a quantity of pages of the document does not exceed a subsetting-optimization threshold. When the quantity of pages does not exceed the threshold, a subsetted font file of the font type is generated. The subsetted file is provided, such as via the spool file, to a print subsystem.

Abstract: Technology described herein is directed to converting display-rendering instructions (e.g., DIRECT2D) into print-rendering instructions (e.g., EMF, WMF, XPS, and SVG). For example, a request to print an item (e.g., document) is received, the item being displayable on an output device when display-rendering instructions are executed. A print render target is created that includes an instructions converter. The display-rendering instructions are routed to the print render target. The instructions converter maps the display-rendering instructions to the print-rendering instructions, which are usable to print the item.

Abstract: The subject disclosure is directed towards a technology in which a first software version (e.g., build or check-in) that corresponds to a failure/regression is automatically identified. Software versions associated with a development order are automatically loaded and tested according to a search plan that narrows in on which version a failure condition first appears. For example, a binary search may be used that looks back to a previous version when a failure is detected on a tested version, or moves to a subsequent version when the failure is not detected. The search plan allows multiple test machines run tests in parallel on different versions, and adapts to the number of test machines available for testing.

Abstract: Various technologies described herein pertain to filling a fill area of a canvas with a source visual object and/or a supplemental visual object to emulate a result of clamping the source visual object onto the fill area of the canvas. A source sub-region of a canvas is filled with the source visual object. Moreover, an extension sub-region of the canvas, which includes at least a part of the fill area outside the source sub-region, is formed based on the source sub-region of the canvas. Further, a supplemental visual object is generated by using a tiling clip on the source visual object and repeated within the extension sub-region of the canvas. The tiling clip specifies a size of the portion of the source visual object used as the supplemental visual object.

Abstract: In one embodiment, a test case run analyzer may filter out failure events with known causes from a test report. The test case run analyzer may receive a test report of a test case run of an application process. The test case run analyzer may automatically identify a failure event in the test case run. The test case run analyzer may automatically compare the failure event to a failure pattern set. The test case run analyzer may filter the test report based on the failure pattern set.

Abstract: Systems and techniques of monitoring, assessing and determining the quality of software components and/or their associated features that may be designed and built to be run on a plurality of hardware devices. Such hardware devices may be devices made by different manufacturers. In addition, certain of these manufacturers may be device partners with the software maker. Software product and/or components may be subjected to test runs on various hardware devices and the results may be correlated. This pass/fail data may also be correlated against a number of additional factors—e.g., the market share of device products for which a software product has a minimum level of acceptable or passing rates.

Abstract: Subject matter described herein is directed to providing font-rendering information (e.g., XPS file) that is usable to print a document. For example, a font file is received that defines a font type included in the document. A determination is made that a quantity of pages of the document does not exceed a subsetting-optimization threshold. When the quantity of pages does not exceed the threshold, a subsetted font file of the font type is generated. The subsetted file is provided, such as via the spool file, to a print subsystem.

Abstract: Test cases are executed by the software engineering test system. The test cases target software products. Test outputs are generated indicating whether the software engineering test system determined the test cases to have passed or failed. Separately, bug records are stored in a first dataset whose records identify corresponding bugs. Records of the test case executions are stored in a second dataset. Records thereof indicate whether a corresponding test case failed when executed. Such records may have bug identifiers entered by a test engineer and corresponding to bugs identified by the test engineer. The first dataset is parsed to identify records of test runs that have failed, and for each such test run record a bug identifier thereof is identified. Statistics such as failure counts are updated for the bugs found in the test run records.

Abstract: Subject matter described herein is directed to providing font-rendering information (e.g., XPS file) that is usable to print a document. For example, a font file is received that defines a font type included in the document. A determination is made that a quantity of pages of the document does not exceed a subsetting-optimization threshold. When the quantity of pages does not exceed the threshold, a subsetted font file of the font type is generated. The subsetted file is provided, such as via the spool file, to a print subsystem.

Abstract: Techniques for determining how to perform a rasterization of printing data. A rasterization facility may receive from a printer driver a request to rasterize printing data in a page description language (PDL) format. The rasterization facility may select a processing unit on which to rasterize the printing data, which may include determining whether to invoke a GPU or a CPU to perform the rasterization. When the GPU is selected, the CPU and GPU may be operated concurrently to perform rasterization. For example, while the GPU is rasterizing a first portion of the printing data, the CPU may determine a next portion to be rasterized, such that the next portion may be made available to the GPU when the GPU is ready to rasterize another portion. The rasterization facility may also convert printing elements of the printing data to a target color space.

Abstract: A conversion tool enables XPS documents to be automatically converted into the Open XPS format and for Open XPS-formatted documents to be automatically converted into the XPS format. The conversion tool may convert content types, package-level relationships, part-level attributes, and image parts into a format supported by either document format.

Abstract: Various technologies described herein pertain to filling a fill area of a canvas with a source visual object and/or a supplemental visual object to emulate a result of clamping the source visual object onto the fill area of the canvas. A source sub-region of a canvas is filled with the source visual object. Moreover, an extension sub-region of the canvas, which includes at least a part of the fill area outside the source sub-region, is formed based on the source sub-region of the canvas. Further, a supplemental visual object is generated by using a tiling clip on the source visual object and repeated within the extension sub-region of the canvas. The tiling clip specifies a size of the portion of the source visual object used as the supplemental visual object.

Abstract: Various embodiments provide a testing infrastructure that abstracts test cases from APIs in a manner that allows for round tripping between production and consumption and APIs.

Abstract: Subject matter described herein is directed to providing font-rendering information (e.g., XPS file) that is usable to print a document. For example, a font file is received that defines a font type included in the document. A determination is made that a quantity of pages of the document does not exceed a subsetting-optimization threshold. When the quantity of pages does not exceed the threshold, a subsetted font file of the font type is generated. The subsetted file is provided, such as via the spool file, to a print subsystem.