Creating Custom Configurations on DTP
Running Test Configurations From the Preference Page
Collecting Coverage from Standalone Applications with Coverage Agent Manager
Other Enhancements
- Support for Visual Studio 2017
- Support for .NET Framework 4.7
- Analyzing web-based projects with Metrics
Updated Code Analysis Rules
The following code analysis rules have been updated to improve the performance of Static Analysis:
| Rule ID | Description |
|---|---|
| SERIAL.XML.SOAFAP-1 | Make sure that type of serialized field/property is compatible with type used in XmlElementAttribute |
| SEC.LGE-2 | Ensure all exceptions are either logged with a standard logger or rethrown |
| PB.STATICFLD-3 | Do not write to static fields from non-static methods |
| EXCEPT.NCSAE-3 | Avoid the use of "catch" on 'Exception', 'SystemException' or 'ApplicationException' |
| CS.BRM.ES-3 | Use string.Empty for empty strings |
| VS.BRM.ES-3 | Use string.Empty for empty strings (added rule for Visual Basic) |
Resolved Bugs and FRs
| Bug/FR ID | Description |
|---|---|
| DT-10623 | dotTest 10.3.2 doesn't release floating license when testing is complete |
| DT-9406 | On 32-bit Windows 7 dotTEST FA cannot analyze a project with target platform set to |
| DT-9403 | Rule map not being honored by DTP Engine for .NET |
| DT-8947 | Not reporting of tests or coverage when running MSTests with coverage |
| DT-8781 | monitorCoverage.bat script template deletes application log directory (accumulation not possible) - change or document this |
