Inspection results are reported in the Code Inspection tab of the Build Results page. Inspections (ReSharper): gathers results of JetBrains ReSharper Code Analysis in your C#, VB.NET, XAML, XML, ASP.NET, JavaScript, CSS, and HTML code. More than 600 Java, HTML, CSS, JavaScript inspections are performed by this runner. Inspections (IntelliJ IDEA): runs code analysis based on IntelliJ IDEA inspections. The following inspections tools are bundled with TeamCity: TeamCity comes with code analysis tools capable of inspecting your source code on the fly, finding and reporting common problems and anti-patterns. You can assign a user to investigate a failed test, or mute this test, so it doesn't affect the build status. Many build runners produce test reports automatically, depending on the settings you configure: Gradle, Maven, IntelliJ IDEA Project, Python, Node.js, NUnit and others. See the list of currently supported testing frameworks. These results are displayed in the build overview. To reduce the feedback time on test failures, it reports detailed test results on the fly whenever possible. TeamCity provides out-of-the-box support for a number of testing frameworks. This section contains articles concerning support of test reports, code inspections, and code coverage in TeamCity. Configuring Test Reports and Code Coverage
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |