You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/userguide/reporters.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,6 +95,24 @@ Providing invalid paths or paths to non-existing files will result in failure wh
95
95
96
96
For details on how to invoke reporter with paths, see the **Coverage reporters** section.
97
97
98
+
# TFS / VSTS Reporter
99
+
If you are using [TFS](https://www.visualstudio.com/tfs/) or [VSTS](https://www.visualstudio.com/team-services/) to do static code analysis for you PLSQL projects and run builds, your code analysis can benefit from code coverage and test results. TFS reporter is designed specifically to [work with Microsoft Team Fundation Server](https://docs.microsoft.com/en-us/vsts/build-release/tasks/test/publish-test-results?view=vsts) report format which is very old version of [JUnit](https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd).
100
+
Main diffrence between standard JUnit is that <testsuite> elements cannot be nested and attribute skipped is not present.
101
+
102
+
utPLSQL provides test reporter to for TFS / VSTS server:
103
+
-`ut_tfs_junit_reporter` - provides an XML output of each test executed per each project test file (package)
0 commit comments