catchorg / catchorg/Catch2

Add option for TeamCity reporter to report SECTIONs

Open
#1,879 2 comments 3 reactions 0 assignees View on GitHub
Tweak request
Dominant language
C++
Stars
21.5k
Forks
3.5k
Avg merge
3d 16h
Merged PRs (30d)
2

Description

**Description**
The JUnit reporter reports SECTIONs.
The TeamCity reporter does not.
Not sure if reporting SECTIONs should always be enabled, but could there be at least an option?

Except for this, I would very much like to use the TeamCity reporter, since it seems to use a lot less memory compared to the JUnit reporter (10 MB vs. 4 GB in my case).

**Additional context**
Tried with latest version, Catch2 2.11.1.

**Compare JUnit report:**
![image](https://user-images.githubusercontent.com/5494429/76091847-a3844100-5fbe-11ea-8e23-09e2ab540b19.png)

**...with TeamCity report:**
![image](https://user-images.githubusercontent.com/5494429/76091665-4f795c80-5fbe-11ea-8d22-9ce20dd5e64e.png)

Contributor guide

Open the contributing guide

Research direction

Start by locating the JUnit and TeamCity reporter implementations and comparing how each handles SECTIONs. Determine how a TeamCity option should be exposed, then verify that enabling it reports SECTIONs while preserving existing behavior when disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.