Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Character

Should be escaped as

' (apostrophe)

|'

\n (line feed)

|n

\r (carriage return)

|r

\u0085 (next line)

|x

\u2028 (line separator)

|l

\u2029 (paragraph separator)

|p

| (vertical bar)

||

[ (opening bracket)

|[

Wiki Markup
{hidden-data

}because of [http://youtrack.jetbrains.net/issue/TW-14069]{hidden-data}

] (closing bracket)

|]

Anchor
commonProperties
commonProperties

...

duration (optional numeric attribute) - sets the test duration to be reported in TeamCity UI. If omitted, the test duration will be calculated from the messages timestamps. If the timestamps are missing, from the actual time the messages were received on the server.
captureStandardOutput (optional boolean attribute) - if true, all the standard output (and standard error) messages received between testStarted and testFinished messages will be considered test output. The default value is false and assumes usage of testStdOut and testStdErr service messages to report the test output.

Note
  • All the other test messages (except for testIgnored) with the same name attribute should appear between the testStarted and testFinished messages (in that order).
  • Currently, the test-related service messages cannot be output with Ant's echo task until flowId attribute is specified.

It is highly recommended to ensure that the pair of test suite + test name is unique within the build.
For advanced TeamCity test-related features to work, test names should not deviate from one build to another (a single test should be reported under the same name in every build). e.g. it's highly unrecommended to include absolute paths in the reported test names.

...

You can also permanently change the build status text for your build. Unlike with progress messages, this change persists even after build has finished.

...

To report build statistics using service messages:

...

Any messages that appear between these two are not parsed as service messages and are effectively ignored.
For server-side processing of service messages, enable/disable service messages also support flowId attribute and will ignore only the messages with the same flowId.

Wiki Markup
{hidden-data

...

}See details in [TW-4436|http://youtrack.jetbrains.net/issue/TW-4436]{hidden-data}

Anchor
ReportingFxCop
ReportingFxCop

...