JetBrains / teamcity-nunit-samples
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
proj
txt
csproj
cmd
gitattributes
targets
Overview of Analyzed Files
Basic stats on analyzed files
Intro
For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

  • The main category contains all manually created source code files that are being used in the production.
  • Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
  • Test source code files are used only for testing of the product. These files are normally not deployed to production.
  • Build and deployment source code files are used to configure or support build and deployment process.
  • Generated source code files are automatically generated files that have not been manually changed after generation.
  • While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
  • Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

main210 LOC (52%) 9 files
test125 LOC (31%) 3 files
generated0 LOC (0%) 0 files
build and deployment60 LOC (15%) 1 file
other5 LOC (1%) 2 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
targets
proj
cmd
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 9 files match defined criteria (210 LOC, 100.0% vs. main code):
    • 3 *.cs files (87 LOC)
    • 1 *.targets files (74 LOC)
    • 3 *.proj files (44 LOC)
    • 2 *.cmd files (5 LOC)
  • " *.cs" is biggest, containing 41.43% of LOC.
  • " *.cmd" is smallest, containing 2.38% of LOC.


*.cs87 LOC (41%) 3 files
*.targets74 LOC (35%) 1 file
*.proj44 LOC (20%) 3 files
*.cmd5 LOC (2%) 2 files
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]ests/.*".
  • 3 files match defined criteria (125 LOC, 59.5% vs. main code):
    • 1 *.csproj files (84 LOC)
    • 2 *.cs files (41 LOC)
  • " *.csproj" is biggest, containing 67.2% of LOC.
  • " *.cs" is smallest, containing 32.8% of LOC.


*.csproj84 LOC (67%) 1 file
*.cs41 LOC (32%) 2 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
csproj
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]csproj".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitignore".
    • files with paths like ".*/[.]gitattributes".
  • 1 file matches defined criteria (60 LOC, 28.6% vs. main code). All matches are in *.csproj files.


*.csproj60 LOC (100%) 1 file
Other Code
txt
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]txt".
    • files with paths like ".*/[.]gitignore".
  • 2 files match defined criteria (5 LOC, 2.4% vs. main code):
    • 1 *.txt files (3 LOC)
    • 1 *.md files (2 LOC)
  • " *.txt" is biggest, containing 60% of LOC.
  • " *.md" is smallest, containing 40% of LOC.


*.txt3 LOC (60%) 1 file
*.md2 LOC (40%) 1 file
Analyzers
Info about analyzers used for source code examinations.

2026-01-18 16:44